I have some systems using Red Hat 5.2 plus raid0145-19981215-2.0.36 with raidtools-19981214-0.90.tar.gz. On each I have six disks configured as a single RAID5 device and with an ext2 filesystem with 4K blocksize and -Rstride=16 (since the raid chunk-size is 64). On running quotacheck (from the quota-1.55-9 RPM from Red Hat 5.2), it writes complete random trash into the "amount used" fields of the quota file: it's clearly picking up not only random block data but also random uid data. This caused people to appear over-quota. Oops. Recompiling quotacheck from source with -DEXT2_DIRECT turned off makes it works fine. (In fact, it's nice and fast despite the fact that it has to walk the filesystem tree itself.) It looks as though libext2fs (or possibly the way quotacheck calls it) is broken when used with one or more of the following: (1) any RAID device (2) any ext2 filesystem with 4K blocks (3) any ext2 filesystem with -Rstride=n I think (1) is unlikely and that it's probably 2 or 3 (but RAID users are mostly likely to tweak those). Has anyone else run into this or can anyone else please try to reproduce it? Once I know exactly what's causing it I'll contact the quota tools maintainer and/or Red Hat. --Malcolm -- Malcolm Beattie <[EMAIL PROTECTED]> Unix Systems Programmer Oxford University Computing Services
