[GRASS-user] Location deletes on restart

GRASS GRASS user
1

Daniel wrote:

Recently the location in which I last worked is deleted when I
restart my computer. I've worked around it by making a backup
copy before I shut down, but is this happening to anyone else?
It's a pretty annoying problem, especially since before I
figured out what was going on and made a proper workaround I
had to complete two rather large projects twice. Running GRASS
6.4.2RC1-3.3-x86_64 from the Geo repository on OpenSUSE 11.4.

so it's fully reproducible?
and the location still exists on the disk after you exit grass
completely? (double check with `ps`, look for Init.sh)
and it is gone directly after reboot? ie before grass is restarted
after a boot?

plenty of free disk space? e2fsck comes up clean?
ssd or traditional hard drive? anything special about the
partition? (it's not symlinked into /var/tmp/ or anything like
that?)
does running "sync" before shutting down help?
waiting >35 sec after shutting down grass before turning off the
computer?

grass itself doesn't go near the boot/shutdown init scripts
so if it happens outside of grass I'm wondering what it could
be..

odd,
Hamish

2

I also find it very odd.

2011/11/10 Hamish <hamish_b@yahoo.com>

so it’s fully reproducible?

So far, yes. I’ve reproduced it three times, sadly twice by accident.

and the location still exists on the disk after you exit grass
completely? (double check with ps, look for Init.sh)

I just tried it this time again. ps -A | grep Init.sh turns up with nothing.

and it is gone directly after reboot? ie before grass is restarted
after a boot?

Yes.

plenty of free disk space?

Several hundred GB.

e2fsck comes up clean?

Never worked with e2fsck before and it looked a little dangerous when I thumbed through the man page… Sadly, I’m kind of short on time today so I can’t read myself into it too much. What are you looking for exactly?

ssd or traditional hard drive?

Normal, traditional hard drive.

anything special about the
partition? (it’s not symlinked into /var/tmp/ or anything like
that?)

Nope.

does running “sync” before shutting down help?

Tried it just now. Didn’t make a difference.

waiting >35 sec after shutting down grass before turning off the
computer?

Had done that every time before… I shut down GRASS, then finished some other projects, then turned off the computer so at least 20 minutes went by.

grass itself doesn’t go near the boot/shutdown init scripts
so if it happens outside of grass I’m wondering what it could
be…

Yes, it definitely is strange, because it’s always the location I worked on last.

I should perhaps mention that I also have GRASS 7 compiled from source, and I’ve worked with both versions on this machine before. However, the phenomenon I’m talking about right now has occured with GRASS 6, I haven’t used 7 in at least three weeks.

3

Okay, I’ve found the problem - embarassing as it is… I have scripts that run before login that are supposed to synchronize my GRASS-DB with the company DB on our server. It looks like the script is removing my location because it doesn’t exist on the server. I’ll have to talk with our administrator about it, but the problem’s definitely ours and not from GRASS :stuck_out_tongue: Sorry for the hubub!

Daniel

4

On Thu, Nov 10, 2011 at 1:07 PM, Daniel Lee <lee@isi-solutions.org> wrote:

Okay, I've found the problem - embarassing as it is... I have scripts that
run before login that are supposed to synchronize my GRASS-DB with the
company DB on our server. It looks like the script is removing my location
because it doesn't exist on the server. I'll have to talk with our
administrator about it, but the problem's definitely ours and not from GRASS
:stuck_out_tongue: Sorry for the hubub!

If that's rsync based, careful with the --delete parameter and slashes...

Glad you found it,
Markus