> Hmm It says the inode doesn't contain a file now. (This is after
> a massive e2fsck run. I had to kill -9 the filesystem)
If you ever want to debug any kind of ext2fs problem, you have to examine
the situation before running e2fsck. It's the job of ext2fs to repair any
bogus state in th
On Sun, Dec 09, 2001 at 10:53:54PM -0500, Roland McGrath wrote:
> Use debugfs so show us the full details of that inode.
Hmm It says the inode doesn't contain a file now. (This is after
a massive e2fsck run. I had to kill -9 the filesystem)
I'll watch for it, and post information if/whe
Use debugfs so show us the full details of that inode. I don't think that
can be anything but bad data written to the inode. That should not be
possible unless an ext2fs bug or something else wrote bad data there, or
you have a bad disk or bad memory or something like that. If e2fsck didn't
fin
I got this a few times while untaring gcc onto a new partition:
ext2fs: /dev/hd0s9: warning: cannot handle large file inode 110459
When I was building, as puked saying it couldn't create a file that
large or something. When I reran make it proceeded fine.
So I know my filesystem is screwed up
Ramadan Kareem or Happy
Festive Season,
Did you visit our Virtual Delivery Outlet? If not Click
Here
Room Service
Deliveries, the delivery service from over 150 restaurants
in Dubai and Abu Dhabi,
Delivered to your
doorstep within the hour.
Room Service @ Your
Service
www.rooms
