I'm not even sure how to describe this, but I'll try. Okay: I have a small NAS device attached to my home LAN which I've been using to keep a large (~300GB) of data files on, but which is near its storage limit. So I've been trying to set up LVM (for the first time) on my 10.0 system, to create a larger archive to copy the data files to. The LVM creation process went well, as far as I can tell, and I ordered an rsync job to duplicate the original archive to the new, expanded one. But after about 36GB of copying, something incredibly weird happened: my original archive vanished from the mount list, and the rsync job stopped with a string of "no such file/directory" errors. I mean, it just *vanished* -- stopped showing up at all when I did a df. Konq started reporting "this directory/file no longer appears to be present" when I tried to navigate to it. And this is on a machine that *no one* else has access to, so I can 99% guarantee there was no human intervention. Even stranger: I couldn't remount the NAS drive for some reason, although using its HTTP access I was able to confirm that it was fine. Eventually, I just gave up and rebooted. And now, this (I should note that my NAS is normally mounted to /archives, and the LVM volume to /archives2): david@linux:/> ls -la /bin/ls: archives: No such file or directory total 35 drwxr-xr-x 27 root root 656 2007-01-30 16:12 . drwxr-xr-x 27 root root 656 2007-01-30 16:12 .. drwxr-xr-x 2 root root 48 2005-11-26 21:45 8thdimension drwxr-xr-x 4 david root 104 2007-01-07 20:18 archives2 drwxr-xr-x 2 root root 2896 2006-12-09 00:15 bin drwxr-xr-x 3 root root 1488 2007-01-07 00:32 boot drwxr-xr-x 11 root root 15660 2007-01-30 21:12 dev drwxr-xr-x 108 root root 9288 2007-01-30 23:11 etc drwxr-xr-x 3 root root 72 2005-11-20 04:48 home drwxr-xr-x 11 root root 4136 2007-01-21 16:46 lib drwxr-xr-x 5 root root 144 2007-01-08 08:43 media drwxr-xr-x 2 root root 48 2005-09-09 12:27 mnt drwxr-xr-x 13 root root 344 2006-08-26 17:03 opt dr-xr-xr-x 140 root root 0 2007-01-30 16:12 proc drwx------ 26 root root 1376 2007-01-30 21:11 root drwxr-xr-x 3 root root 9760 2007-01-30 19:47 sbin drwxr-xr-x 2 root root 48 2006-06-19 19:35 sg1 drwxr-xr-x 5 root root 120 2005-11-19 20:35 srv drwxr-xr-x 11 david root 4096 2007-01-27 00:29 storage drwxr-xr-x 2 root root 48 2005-09-09 05:59 subdomain drwxr-xr-x 10 root root 0 2007-01-30 16:12 sys drwxrwxrwt 31 root root 2848 2007-01-30 23:00 tmp drwxr-xr-x 15 root root 416 2006-11-14 09:42 usr drwxr-xr-x 14 root root 360 2005-11-19 19:34 var david@linux:/> sudo mkdir /archives mkdir: cannot create directory `/archives': File exists david@linux:/> ls /archives /bin/ls: /archives: No such file or directory david@linux:/> Okay: If I mount the NAS device to /archives, the mount command succeeds. It shows up in df as mounted, and shows me the NAS device's format and current space used/avail. But any attempt to ls /archives shows it as not existing. So I umounted the NAS device, and tried again. And tried re-creating it with mkdir. And the results, you've seen above. I am *stumped.* This string of behaviors makes *no* sense at all. Has anyone else ever encountered anything like this? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David McMillan wrote:
I'm not even sure how to describe this, but I'll try. Okay: I have a small NAS device attached to my home LAN which I've been using to keep a large (~300GB) of data files on, but which is near its storage limit. So I've been trying to set up LVM (for the first time) on my 10.0 system, to create a larger archive to copy the data files to. The LVM creation process went well, as far as I can tell, and I ordered an rsync job to duplicate the original archive to the new, expanded one. But after about 36GB of copying, something incredibly weird happened: my original archive vanished from the mount list, and the rsync job stopped with a string of "no such file/directory" errors. I mean, it just *vanished* -- stopped showing up at all when I did a df. Konq started reporting "this directory/file no longer appears to be present" when I tried to navigate to it. And this is on a machine that *no one* else has access to, so I can 99% guarantee there was no human intervention. Even stranger: I couldn't remount the NAS drive for some reason, although using its HTTP access I was able to confirm that it was fine. Eventually, I just gave up and rebooted. And now, this (I should note that my NAS is normally mounted to /archives, and the LVM volume to /archives2):
david@linux:/> ls -la /bin/ls: archives: No such file or directory total 35 drwxr-xr-x 27 root root 656 2007-01-30 16:12 . drwxr-xr-x 27 root root 656 2007-01-30 16:12 .. drwxr-xr-x 2 root root 48 2005-11-26 21:45 8thdimension drwxr-xr-x 4 david root 104 2007-01-07 20:18 archives2 drwxr-xr-x 2 root root 2896 2006-12-09 00:15 bin drwxr-xr-x 3 root root 1488 2007-01-07 00:32 boot drwxr-xr-x 11 root root 15660 2007-01-30 21:12 dev drwxr-xr-x 108 root root 9288 2007-01-30 23:11 etc drwxr-xr-x 3 root root 72 2005-11-20 04:48 home drwxr-xr-x 11 root root 4136 2007-01-21 16:46 lib drwxr-xr-x 5 root root 144 2007-01-08 08:43 media drwxr-xr-x 2 root root 48 2005-09-09 12:27 mnt drwxr-xr-x 13 root root 344 2006-08-26 17:03 opt dr-xr-xr-x 140 root root 0 2007-01-30 16:12 proc drwx------ 26 root root 1376 2007-01-30 21:11 root drwxr-xr-x 3 root root 9760 2007-01-30 19:47 sbin drwxr-xr-x 2 root root 48 2006-06-19 19:35 sg1 drwxr-xr-x 5 root root 120 2005-11-19 20:35 srv drwxr-xr-x 11 david root 4096 2007-01-27 00:29 storage drwxr-xr-x 2 root root 48 2005-09-09 05:59 subdomain drwxr-xr-x 10 root root 0 2007-01-30 16:12 sys drwxrwxrwt 31 root root 2848 2007-01-30 23:00 tmp drwxr-xr-x 15 root root 416 2006-11-14 09:42 usr drwxr-xr-x 14 root root 360 2005-11-19 19:34 var david@linux:/> sudo mkdir /archives mkdir: cannot create directory `/archives': File exists david@linux:/> ls /archives /bin/ls: /archives: No such file or directory david@linux:/>
Okay: If I mount the NAS device to /archives, the mount command succeeds. It shows up in df as mounted, and shows me the NAS device's format and current space used/avail. But any attempt to ls /archives shows it as not existing. So I umounted the NAS device, and tried again. And tried re-creating it with mkdir. And the results, you've seen above. I am *stumped.* This string of behaviors makes *no* sense at all. Has anyone else ever encountered anything like this?
Addendum: Even after rebooting again, and re-mounting /archives... david@linux:/> df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 241828 12 241816 1% /dev/shm /dev/hda3 83452412 10284060 68929204 13% /storage //192.168.0.150/archives 312492032 306774016 5718016 99% /archives david@linux:/> ls /archives /bin/ls: /archives: No such file or directory david@linux:/> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-01-30 at 23:55 -0500, David McMillan wrote:
David McMillan wrote:
I'm not even sure how to describe this, but I'll try. Okay: I have a small NAS device attached to my home LAN which I've been using to keep a large (~300GB) of data files on, but which is near its storage limit. So I've been trying to set up LVM (for the first time) on my 10.0 system, to create a larger archive to copy the data files to. The LVM creation process went well, as far as I can tell, and I ordered an rsync job to duplicate the original archive to the new, expanded one. But after about 36GB of copying, something incredibly weird happened: my original archive vanished from the mount list, and the rsync job stopped with a string of "no such file/directory" errors. I mean, it just *vanished* -- stopped showing up at all when I did a df. Konq started reporting "this directory/file no longer appears to be present" when I tried to navigate to it. And this is on a machine that *no one* else has access to, so I can 99% guarantee there was no human intervention. Even stranger: I couldn't remount the NAS drive for some reason, although using its HTTP access I was able to confirm that it was fine. Eventually, I just gave up and rebooted. And now, this (I should note that my NAS is normally mounted to /archives, and the LVM volume to /archives2):
Can you access some debug info on the NAS through the HTTP interface? E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hans van der Merwe wrote:
On Tue, 2007-01-30 at 23:55 -0500, David McMillan wrote:
David McMillan wrote:
I'm not even sure how to describe this, but I'll try. Okay: I have a small NAS device attached to my home LAN which I've been using to keep a large (~300GB) of data files on, but which is near its storage limit. So I've been trying to set up LVM (for the first time) on my 10.0 system, to create a larger archive to copy the data files to. The LVM creation process went well, as far as I can tell, and I ordered an rsync job to duplicate the original archive to the new, expanded one. But after about 36GB of copying, something incredibly weird happened: my original archive vanished from the mount list, and the rsync job stopped with a string of "no such file/directory" errors. I mean, it just *vanished* -- stopped showing up at all when I did a df. Konq started reporting "this directory/file no longer appears to be present" when I tried to navigate to it. And this is on a machine that *no one* else has access to, so I can 99% guarantee there was no human intervention. Even stranger: I couldn't remount the NAS drive for some reason, although using its HTTP access I was able to confirm that it was fine. Eventually, I just gave up and rebooted. And now, this (I should note that my NAS is normally mounted to /archives, and the LVM volume to /archives2):
Can you access some debug info on the NAS through the HTTP interface?
Rather little, I'm afraid. But I'm able to access the NAS device via Samba normally from my Windows systems on the same LAN, and my SUSE 10.0 system can still access the NAS via its FTP service (which I'm currently using to pull the information off). Also, I've found some more odd behavior: I experimented by creating a whole new empty directory and mounting the NAS device to it. The moment I mounted the NAS device to it, *that* directory vanished from the ls display, but showed up in df. When I umounted, ls started showing it again. It's almost as if the act of mounting something to the directory is causing the directory to 'get lost,' somehow. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David McMillan wrote:
Rather little, I'm afraid.
I think personnally you should be very carefull not to erase your data by mistake. You should go to init 1 (maintenance mode, no network) and double check your directories, just in case there could be some soft or hard links around. I once manage to kill my original directory during backup to an usb device. I don't exactly understand what happen, but I had too many cross links for sure (the result was all the files with a zero lenght on the two medias starting from a simple copy with konqueror) your problem is probably not the same as mine, but seems odd enough to be carefull :-) jdd -- http://www.dodin.net Votez pour nous, merci - vote for us, thanks :-) http://musique.sfrjeunestalents.fr/artiste/Magic-Alliance/ http://photo.sfrjeunestalents.fr/artiste/jddphoto/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd wrote:
David McMillan wrote:
Rather little, I'm afraid.
I think personnally you should be very carefull not to erase your data by mistake.
Oh, yes indeed. Which is why I made doubly sure the NAS was unmounted before I tried rm'ing the directory. Fortunately for me, the NAS device has an FTP server as well as a Samba, so I'm currently using that to copy my files before experimenting much further.
You should go to init 1 (maintenance mode, no network) and double check your directories, just in case there could be some soft or hard links around.
I once manage to kill my original directory during backup to an usb device. I don't exactly understand what happen, but I had too many cross links for sure (the result was all the files with a zero lenght on the two medias starting from a simple copy with konqueror)
Ick. So far, it looks like my luck is better than that. <crossed fingers>
your problem is probably not the same as mine, but seems odd enough to be carefull :-)
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 31 January 2007 09:16:37 am David McMillan wrote:
Can you access some debug info on the NAS through the HTTP interface?
Rather little, I'm afraid. But I'm able to access the NAS device via Samba normally from my Windows systems on the same LAN, and my SUSE 10.0 system can still access the NAS via its FTP service (which I'm currently using to pull the information off). Also, I've found some more odd behavior: I experimented by creating a whole new empty directory and mounting the NAS device to it. The moment I mounted the NAS device to it, *that* directory vanished from the ls display, but showed up in df. When I umounted, ls started showing it again. It's almost as if the act of mounting something to the directory is causing the directory to 'get lost,' somehow.
How full is the NAS? More than 90%? More than 95%? If its too full you may be seeing your performance drop to slower than molasses at -40F. If you came back in an hour would the mount point be viewable? If its too full, can you copy anything off to a Windows machine to free up some space on the NAS for the real important info to be backed up? Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2007-01-31 at 10:16 -0500, David McMillan wrote:
Also, I've found some more odd behavior: I experimented by creating a whole new empty directory and mounting the NAS device to it. The moment I mounted the NAS device to it, *that* directory vanished from the ls display, but showed up in df. When I umounted, ls started showing it again. It's almost as if the act of mounting something to the directory is causing the directory to 'get lost,' somehow.
I have two wild ideas: run an fsck on the umounted root partition (you will have to do it from a live dvd or rescue system), and try mounting somewhere not directly under /, but perhaps under /mnt, for instance. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFwT/htTMYHG2NR9URApsbAJ95KLXgw3fvKuhmlYHFvwB/oKT6dwCeNOvy Dk9AR6ciMJD8SBPMoa9aSzQ= =Mwxe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R. -
David McMillan -
Hans van der Merwe -
jdd -
S Glasoe