Messages in this thread | | | From | "Khimenko Victor" <> | Date | Sun, 27 Jun 1999 05:49:44 +0400 (MSD) | Subject | Re: Corrupted partitions |
| |
In <Pine.LNX.4.10.9906261130550.4630-100000@wr5z.localdomain> Thomas Molina (tmolina@home.com) wrote: > I can confirm that e2fsck recreates the lost+found directory. It > happens to me occasionally since I have two partitions used for > creating/writing CDs. I usually end up deleting lost+found in the > process. However, on my system e2fsck only creates a "standard" > 1024-size lost+found instead of the 12288-size directory.
Understandable. If you create lost+font in emergency you'll create small standard directory to minimally affect existing system.
> On Sat, 26 Jun 1999, Riley Williams wrote:
>> Hang on! In an earlier email, you said that the reason that mke2fs >> preallocates 12 blocks to lost+found is because e2fsck has problems >> allocating blocks when fixing a corrupted file system, but now you >> state that no such problem exists !!! Which is it? >> >> > If you're easily amused, you can take a scratch partition, put >> > some data on it, use debugfs to clri the root directory, and >> > then run e2fsck and watch it recover from the damage. It will >> > recreate a root directory and a lost+found directory, and put >> > everything that used to be in the root directory into >> > lost+found. Aside from the names of the directories and files in >> > the root directory, no actual data will be lost. >> >> I don't have any spare scratch partitions to try anything like that >> on, and I wasn't willing to scramble any of my production systems just >> to find out the answer, hence my asking on here...
> - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |