> Sorry for replying to the list, but Mouse refuses to accept mails
> from .de domains.
Yeah, I should train myself to stop responding to list mail from .de
addresses, or at least use something like my netbsd.org address, until
and unless .de...no *smack* bad Mouse! No ranting onlist!
>> If you
Sorry for replying to the list, but Mouse refuses to accept mails from .de
domains.
> If you think that particular problem might be it I have a
> test program you might want, designed to catch just such things.
Yes, I could try that on a spare drive.
>>> Can there be some weird file system inconsistency fsck doesn't spot?
>> Yes. Well, almost certainly.
> So, in case we experience more panics under load on monday, would it
> make sense to dump/newfs/restore the file system? I.e., can there be
> any inconsistencies that "survive" a dump/restor
e...@math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) writes:
>EF> Can there be some weird file system inconsistency fsck doesn't spot?
>dM> Yes. Well, almost certainly.
>So, in case we experience more panics under load on monday, would it make
>sense to dump/newfs/restore the file system? I.e., c
EF> Can there be some weird file system inconsistency fsck doesn't spot?
dM> Yes. Well, almost certainly.
So, in case we experience more panics under load on monday, would it make
sense to dump/newfs/restore the file system? I.e., can there be any
inconsistencies that "survive" a dump/restore?
> On a FFSv2/WAPBL file system successfully fsck -f'd less than two hours
> before, I got a "bad dir: mangled entry" panic.
> I fsck'd again, finding missing dot/dotdot entries [...]
> Just within minutes after going live again, I experienced the same panic,
> and fsck found missing dot/dotdot in
[I tried to send this to mouse in private email, but he refuses to accept it]
> I'd have a close look at the containing directory.
[Asterisks denote information manually hidden for privacy.
The filenames, owner and group names all make sense.]
I=158304666 MODE=40770 SIZE=512
MTIME=Oct 18
> If your filesystem uses 256K or larger blocks,
> those two inodes fall into the same block;
No, it uses 16k blocks.
>> I'm wondering if perhaps it got the same inode or the same disk
>> block or some such.
> No. The directory that twice caused a panic because of missing
> dot/dotdot was inode 463357837, the one with the two entries pointing
> to unallocated inodes is inode 158304666, the two unallocated inodes
> Has the place you're getting the odd EBADF errors been created after
> you deleted the former mystery?
Probably yes (fsdb didn't give me the birth time, but ctime and mtime are
identical and later than the last fsck/deletion of the missing-dot/dotdot
dirctory.
> I'm wondering if perhaps it got
>> What do you get those errors from? find(1)?
> Yes.
> What I've found out so far (from using fsdb) is that those two
> directory entries (one directory and one regular file) point to
> unallocated inodes.
Okay, that's weird. fsck should have caught that - indeed, that's what
you'll see if yo
> What do you get those errors from? find(1)?
Yes.
What I've found out so far (from using fsdb) is that those two directory
entries (one directory and one regular file) point to unallocated inodes.
> I'm getting two "Bad file descriptor" errors, one on a directory and
> another on a regular file, both in the same directory. What do you
> suggest to do?
Hm.
What do you get those errors from? find(1)? I think the first thing
I'd try to do is provoke them deliberately by hand - eg, try usin
> I'd suggest poking around the oddities with fsdb or some such userland
> tool.
I'll try that.
> I'd also have suggested using clri (and then fsck) rather than
> rmdir to deal with the other directory, but that's water under the
> bridge now. (rmdir writes to places other than the directory bein
> Can there be some weird file system inconsistency fsck doesn't spot?
Yes. Well, almost certainly. When I was writing the program that
became resize_ffs when it was imported into NetBSD, I had a bug which
led to the kernel panicking when using the resized filesystem. jtk
found it - but the rel
On a FFSv2/WAPBL file system successfully fsck -f'd less than two hours
before, I got a "bad dir: mangled entry" panic.
I fsck'd again, finding missing dot/dotdot entries and a bunch of unconnected
files.
Just within minutes after going live again, I experienced the same panic,
and fsck found mis
16 matches
Mail list logo
