[DRBD-user] Another oops!
bthomas at wolfgeek.net
Tue Feb 10 23:47:36 CET 2004
Hmm, good point. I wish I had the oops; it would probably help
tremendously debugging this no matter what. But from looking at the
code as you suggested, it may be that with all the NFS traffic this
guy receives we have an issue with reiserfs, and that was bad enough
to cause an oops.
I don't think it's the tl-size problem, as that before had a pretty
I'll do some further investigation, thanks for the pointers.
On Tue, Feb 10, 2004 at 10:41:53PM +0100, Lars Ellenberg wrote:
> in the above log excerpt, I don't see drbd complaining about
> anything. drbd(43,1) is mentioned by reiserfs as its device.
> If you want to read some comments, have a look at
> /usr/src/linux/fs/reiserfs/inode.c and search for "reiserfs_read_inode2"
> in reiserfs warning messages. To me this smells like reiserfs corruption.
> and, reiserfs asked you to fsck...
> maybe you need to fsck after each failover, even with reiserfs.
> maybe reiserfs just does not like HUGE partitions, especially if
> it has to share it with knfsd, and you have *many* interrupts ...
> Or did you mean you got an oops related to strange drbd "barrier"
> packets, like the one you showed us before?
> In that case: are you sure that your tl-size is good, on both nodes?
> I suggest tl-size 5000 or even 12000 or some such.
> If you ever encounter "tl-size too small!" message: it is too small.
> (this is because in 0.6 it is still an array;
> in 0.7 we use a dynamic list for it)
> Lars Ellenberg
> drbd-user mailing list
> drbd-user at lists.linbit.com
More information about the drbd-user