Re: SOS: restore deleted file on ext3 system; CORRECTION--it's reiserfs

Re: SOS: restore deleted file on ext3 system; CORRECTION--it's reiserfs

[James Miller]

I made a mistake about the filesystem on the machine.  It's reiserfs, not ext3.  reiser 3.x, I believe.  One large partition on the machine (/dev/hda2 = 38GB; hda1 is swap).

James

>-----Original Message-----
>From: James Miller [mailto:jamtat@mailsnare.net]
>Sent: Friday, January 20, 2006 09:25 AM
>To: linux-newbie@vger.kernel.org
>Subject: SOS: restore deleted file on ext3 system
>
>I spent all day yesterday revising a chapter of a work I'm writing.  Since I've had trouble ftp'ing files to/from my ftp server, I just emailed the file to myself so I could access it from the library where I was working.  Unfortunately, I told the browser to open the file with the default application (OpenOffice) when I loaded the file from email, rather than having it save it to disk.  I failed to note that, therefore, the file I was editing was located in the /tmp directory.  I finished editing, having saved numerous times while I worked, and shut down the computer.  Today, when I started the system I realized my error and understood that, since I'm using a Debian variant (Xandros), and since Debian's habit is to delete the contents of /tmp on each reboot, the file I spent all day yesterday working on is simply gone.  The system uses the ext3 filesystem, btw.  Can anyone help me to r
 ecover this file so I don't end up having wasted a whole day?  Any suggestions will be greatly appreciated.
>
>Thanks, James
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.linux-learn.org/faqs
>


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: SOS: restore deleted file on ext3 system; CORRECTION--it's reiserfs

[Carl]

At 16:05 20/01/2006, James Miller wrote:
>I made a mistake about the filesystem on the machine.  It's 
>reiserfs, not ext3.  reiser 3.x, I believe.  One large partition on 
>the machine (/dev/hda2 = 38GB; hda1 is swap).


google undelete+reiser 


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

tune2fs question

[James Miller]

I've recently succeeded in installing a Linux to a USB flash drive and, 
more importantly, booting to that drive using a floppy disk. A problem I 
have run into with tunefs needs addressing now. On the machine where I 
installed Linux, the drive was seen as /dev/sdb1. Apparently when I 
formatted the flash drive (ext2), some information regaridng the location 
of the drive was recorded for subsequent use. Now, when I reboot with the 
drive in a different system where it is actually /dev/sda1, e2fsck gives 
some error messages and wants to mount it read-only. I'm thinking that if 
I can change the system's understanding of the device file name, this 
problem might go away. Having looked over documentation (manpages) for 
e2fsck and tune2fs, I'm not finding how I could do this. Can anyone offer 
pointers on how I might get these ext2 filesystem utilities to be aware 
that the target device is not /dev/sdb1 but /dev/sda1?

On recovering a deleted file from reiserfs--the subject of my last post: I 
can confirm it is possible by rebuilding the directory tree. But I can 
also affirm that it is something you should NOT do on a root filesystem (a 
separate, data partition is the ideal target). It will corrupt important 
system files/modules if you do it on a root filesystem, necessitating a 
likely reinstall of the OS. On my system the kernel remains intact, but 
important modules are hosed, and maybe other key files. Think over 
carefully whether the file you want to recover is important enough to 
justify basically hosing the rest of your system.

James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: tune2fs question

[James Miller]

Maybe it's bad form to answer your own questions, but on the chance it may 
help some other clueless newbie, I'll do so. It turns out the problem was 
a bogus /etc/fstab entry pointing to /dev/sdb1 as the root filesystem. 
Once I corrected that, changing it to /dev/sda1, e2fsck ran successfully, 
the HD got mounted rw like it was to supposed, and things began running 
according to plan.

James

On Wed, 1 Feb 2006, James Miller wrote:

> I've recently succeeded in installing a Linux to a USB flash drive and, more 
> importantly, booting to that drive using a floppy disk. A problem I have run 
> into with tunefs needs addressing now. On the machine where I installed 
> Linux, the drive was seen as /dev/sdb1. Apparently when I formatted the flash 
> drive (ext2), some information regaridng the location of the drive was 
> recorded for subsequent use. Now, when I reboot with the drive in a different 
> system where it is actually /dev/sda1, e2fsck gives some error messages and 
> wants to mount it read-only. I'm thinking that if I can change the system's 
> understanding of the device file name, this problem might go away. Having 
> looked over documentation (manpages) for e2fsck and tune2fs, I'm not finding 
> how I could do this. Can anyone offer pointers on how I might get these ext2 
> filesystem utilities to be aware that the target device is not /dev/sdb1 but 
> /dev/sda1?
>
> On recovering a deleted file from reiserfs--the subject of my last post: I 
> can confirm it is possible by rebuilding the directory tree. But I can also 
> affirm that it is something you should NOT do on a root filesystem (a 
> separate, data partition is the ideal target). It will corrupt important 
> system files/modules if you do it on a root filesystem, necessitating a 
> likely reinstall of the OS. On my system the kernel remains intact, but 
> important modules are hosed, and maybe other key files. Think over carefully 
> whether the file you want to recover is important enough to justify basically 
> hosing the rest of your system.
>
> James
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs