Is there any way I can undelete? We have SuSE 8.0 with reiser. Urgent! Tia, Steve. __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
Hello Steve, On Saturday 14 December 2002 12:11, steve sheriff wrote:
Is there any way I can undelete? We have SuSE 8.0 with reiser. Urgent!
AFAIK this is not possible. I hope you have backup.
Tia, Steve.
Regards, Cees.
On Sat, 14 Dec 2002 16:01:45 +0100 Cees van de Griend <cees-list@griend.xs4all.nl> wrote:
Hello Steve,
On Saturday 14 December 2002 12:11, steve sheriff wrote:
Is there any way I can undelete? We have SuSE 8.0 with reiser. Urgent!
AFAIK this is not possible. I hope you have backup.
Regarding this, I'm not sure how impossible it is. This is what happened to me. In my previous setup, I had /dev/hda4 setup as a separate root partition. When I installed suse8.1, I converted /dev/hda4 to /home. I thought I deleted everything, and formatted it as reiserfs. Anyways, I just compiled a new kernel, and to test it, I put it into my lilo.conf where an old kernel was commented out, and was using /dev/hda4 as root. Well I went to boot the new kernel, and guess what!!!! It somehow found the old root filesystem on /dev/hda4 and actually booted!!! I was thrown off because my old root password worked, but my new one didn't. I was baffled until I discovered that I was booting my /home !!! I havn't investigated this further, but old files are on your drive until you use a "wipe" utility. -- use Perl; #powerful programmable prestidigitation
On Saturday 14 December 2002 16:01, Cees van de Griend wrote:
Hello Steve,
On Saturday 14 December 2002 12:11, steve sheriff wrote:
Is there any way I can undelete? We have SuSE 8.0 with reiser. Urgent!
AFAIK this is not possible. I hope you have backup.
Tia, Steve.
Regards, Cees.
Hi. reiserfsck has restored everything I lost but I can only see it in runlevel 1 where /home is totally visible again. Back in runlevel 3 or 5 /home exists but contains no directories and I can't write to it not even as root. I copied /home to /usr in runlevel 1 where it is readable and so burnable to a cd. Question: why should /home be unwritable whilst /usr is? The crash happened during a power failure but I'd like a software answer that we can avoid problems in future. Cheers, Steve.
On Monday 16 December 2002 15.11, fsanta wrote:
Hi. reiserfsck has restored everything I lost but I can only see it in runlevel 1 where /home is totally visible again. Back in runlevel 3 or 5 /home exists but contains no directories and I can't write to it not even as root. I copied /home to /usr in runlevel 1 where it is readable and so burnable to a cd. Question: why should /home be unwritable whilst /usr is? The crash happened during a power failure but I'd like a software answer that we can avoid problems in future. Cheers, Steve.
Which mount options are in effect in runlevel 1 and 3 respectively? Therein lies the answer, methinks. Try "grep home /proc/mounts" once for each runlevel
On Monday 16 December 2002 15:11, fsanta wrote:
Is there any way I can undelete? We have SuSE 8.0 with reiser. Urgent!
AFAIK this is not possible. I hope you have backup.
reiserfsck has restored everything I lost but I can only see it in runlevel 1 where /home is totally visible again.
Ahh, you had an crash. I asumed you had manually deleted the files. Sorry, I jumped to the wrong conclusion.
Back in runlevel 3 or 5 /home exists but contains no directories and I can't write to it not even as root. I copied /home to /usr in runlevel 1 where it is readable and so burnable to a cd. Question: why should /home be unwritable whilst /usr is?
Probaly you have /usr on your root partition and /home on a different partition. If i recall correctly, in run level 1 (singel user mode), all partions except the root partiton are mounted read-only.
The crash happened during a power failure but I'd like a software answer that we can avoid problems in future.
Uhh. Probably software isn't the anser for an hardware problem. Think about UPS-es. A journalling filesystem is a usefull tool, not a garanty, during a power failure.
Cheers, Steve.
Regards, Cees.
On Mon, 16 Dec 2002 16:36:46 +0100 Cees van de Griend <cees-list@griend.xs4all.nl> wrote:
The crash happened during a power failure but I'd like a software answer that we can avoid problems in future.
Uhh. Probably software isn't the anser for an hardware problem. Think about UPS-es. A journalling filesystem is a usefull tool, not a garanty, during a power failure.
It isn't normal to get that kind of filesystem corruption just because the power went out. I've pulled the plug on my machine, and I may lose recent information, but my filesystem is still there. Do you think it's possible for reiserfs to go down that badly? Maybe his hard drive or controller is getting flaky? -- use Perl; #powerful programmable prestidigitation
On Monday 16 December 2002 23:44, zentara wrote:
On Mon, 16 Dec 2002 16:36:46 +0100
Cees van de Griend <cees-list@griend.xs4all.nl> wrote:
The crash happened during a power failure but I'd like a software answer that we can avoid problems in future.
Uhh. Probably software isn't the anser for an hardware problem. Think about UPS-es. A journalling filesystem is a usefull tool, not a garanty, during a power failure.
It isn't normal to get that kind of filesystem corruption just because the power went out.
I can't comment, I don't have enough data. For example what was de server doing just before the crash, which processes ran, which processes where writing to the disk, etc...
I've pulled the plug on my machine, and I may lose recent information, but my filesystem is still there.
I can't comment, I don't have enough data. I can say that on my home machine I've done the same, but for a server the load is very light and there is normally little writing to disks.
Do you think it's possible for reiserfs to go down that badly? Maybe his hard drive or controller is getting flaky?
I think you have the wrong idea about journaling filesystems. Normally you are right and normally a journaling filesystem should recover quickly after an crash. But there are no garanties. Journaling is for a quick recover after an crash, so you have a 'more or less' working system. (I don't know if you have ever waited for a fsck on an 60 GB ext2 file system - I have and it's a very long time - but if you have you will apriciated journaling filesystems.) Of course, a journaling filesystem tries to get the old data back and normaly it does a very good job, but there are senarios in which this doesn't work. Regards, Cees.
participants (5)
-
Anders Johansson -
Cees van de Griend -
fsanta -
steve sheriff -
zentara