Hi list,
I had to exchange a harddisk, so I moved the GRASS-locations from a reiserfs to a fat32 drive. When restoring the system, I receive "Warning: this is not a valid mapset" without any further hint.
GRASS was build out of cvs and the permissions on files and directories are set identical. Any idea what I may have messed up?
Thanks in advance,
Mit freundlichen Grüßen / With kindest regards
Stefan Paulick
http://www.urbeli.com
mailto://stefan.paulick@urbeli.com
/*----------------------*/
Paulick Consult wrote:
I had to exchange a harddisk, so I moved the GRASS-locations from a reiserfs
to a fat32 drive. When restoring the system, I receive "Warning: this is not
a valid mapset" without any further hint.GRASS was build out of cvs and the permissions on files and directories are
set identical. Any idea what I may have messed up?
Copying to a FAT filesystem and back won't retain ownership or
permissions, and may result in the case of filenames being changed.
I don't know where that error originates, but from its wording I
suspect that the most likely cause is that one or more files or
directories have had their case changed.
--
Glynn Clements <glynn@gclements.plus.com>
Hello Glynn,
On Wed, 31 Aug 2005 20:46:57 +0100 Glynn Clements
<glynn@gclements.plus.com> wrote:
Paulick Consult wrote:
> I had to exchange a harddisk, so I moved the GRASS-locations from a
> reiserfs to a fat32 drive. When restoring the system, I receive
> "Warning: this is not a valid mapset" without any further hint.
>
> GRASS was build out of cvs and the permissions on files and
> directories are set identical. Any idea what I may have messed up?Copying to a FAT filesystem and back won't retain ownership or
permissions, and may result in the case of filenames being changed.I don't know where that error originates, but from its wording I
suspect that the most likely cause is that one or more files or
directories have had their case changed.
I can confirm this. While copying back from a Fat-formated USB-stick,
the PROJ_INFO, DEFAULT_WIND and WIND-Files were lower case. Change
them to upper-case again and everything works again.
Best
Stephan
--
GDF Hannover - Solutions for spatial data analysis and remote sensing
Hannover Office - Mengendamm 16d - D-30177 Hannover
Internet: www.gdf-hannover.de - Email: holl@gdf-hannover.de
Phone : ++49-(0)511.39088507 - Fax: ++49-(0)511.39088508
Hello Glynn and Stephan,
thank you very much for your help! The copy showed the following filenames:
/PERMANENT/DEFAULT_WIND
/PERMANENT/myname
/PERMANENT/PROJ_INFO
/PERMANENT/PROJ_UNITS
/PERMANENT/wind
After renaming to capital letters it worked as usual. Is there a understandable reason why these two files and only those two changed to minor letters?
Adittionally, it would be great if the grass error message would point out what did lead to the failure.
Mit freundlichen Grüßen / With kindest regards
Stefan Paulick
http://www.urbeli.com
mailto://stefan.paulick@urbeli.com
/*----------------------*/
Stephan Holl schrieb:
Hello Glynn,
On Wed, 31 Aug 2005 20:46:57 +0100 Glynn Clements
<glynn@gclements.plus.com> wrote:Paulick Consult wrote:
> I had to exchange a harddisk, so I moved the GRASS-locations from a
> reiserfs to a fat32 drive. When restoring the system, I receive
> "Warning: this is not a valid mapset" without any further hint. > > GRASS was build out of cvs and the permissions on files and
> directories are set identical. Any idea what I may have messed up?Copying to a FAT filesystem and back won't retain ownership or
permissions, and may result in the case of filenames being changed.I don't know where that error originates, but from its wording I
suspect that the most likely cause is that one or more files or
directories have had their case changed.I can confirm this. While copying back from a Fat-formated USB-stick,
the PROJ_INFO, DEFAULT_WIND and WIND-Files were lower case. Change
them to upper-case again and everything works again.Best
Stephan--
GDF Hannover - Solutions for spatial data analysis and remote sensing
Hannover Office - Mengendamm 16d - D-30177 Hannover
Internet: www.gdf-hannover.de - Email: holl@gdf-hannover.de
Phone : ++49-(0)511.39088507 - Fax: ++49-(0)511.39088508_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5
Paulick Consult wrote:
thank you very much for your help! The copy showed the following filenames:
/PERMANENT/DEFAULT_WIND
/PERMANENT/myname
/PERMANENT/PROJ_INFO
/PERMANENT/PROJ_UNITS
/PERMANENT/windAfter renaming to capital letters it worked as usual. Is there a
understandable reason why these two files and only those two changed to
minor letters?
It's the DOS 8.3 filename limit.
The default Linux mount options for VFAT (Win95) filesystems only
create an extended filename where necessary (i.e. longer than 8
characters, mixed case, contains spaces etc), otherwise they only
create a short filename. Short filenames don't preserve case; they are
always stored on disk using upper-case, but Linux treats them as lower
case (lower-case filenames are a lot more common).
You can change the behaviour with the "shortname" mount option:
shortname=[lower|win95|winnt|mixed]
Defines the behaviour for creation and display of filenames
which fit into 8.3 characters. If a long name for a file exists,
it will always be preferred display. There are four modes:
lower Force the short name to lower case upon display; store a
long name when the short name is not all upper case.
win95 Force the short name to upper case upon display; store a
long name when the short name is not all upper case.
winnt Display the shortname as is; store a long name when the
short name is not all lower case or all upper case.
mixed Display the short name as is; store a long name when the
short name is not all upper case.
More generally, don't "back up" Unix directories to a VFAT filesystem
by copying; create a tar file instead. Apart from issues of case,
copying to a VFAT filesystem will lose ownership, permissions, and
(some) timestamps, and won't handle links correctly.
--
Glynn Clements <glynn@gclements.plus.com>