nate <mailto:[EMAIL PROTECTED]> wrote on Thursday, 16 January 2003 07:37:
> Ryan Babchishin said: > >> That's the best suggestion I've heard yet... Do you know of any risks >> involved in repairing something that you know is in error, while the >> fs is mounted? > > worst case is you damage/destroy data on that particular inode. I > think multiple files/directories can exist in a single inode. The > only way I can think of off the top of my head is use ls -i to find > what files are on what inodes, so something like > > ls -Rli >/tmp/files.list > > > nate Would you mind expanding on that please - my understanding from older unix filesystems was that two files with the same inode were the same file just linked to two names. On the other hand, if a directory and a regular file was using the same inode then chaos would ensue. It used to be that the worst case was disk blocks allocated to multiple files or directories - or allocated and in the free list at the same time. I don't understand the "free blocks count corrupted" message but perhaps you (Ryan) should take a quick look at the kernel source to find out what it means, and how it attempts to recover. Maybe if it does not trust a block to be free it wont use it - which would be a failsafe approach and just gradually chew up the available space. But 10000 times? Cameron. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
