On Thu, 10 Mar 2011, Manuel Bouyer wrote: > On Thu, Mar 10, 2011 at 06:59:41PM +0100, Ignatios Souvatzis wrote: > > Hi, > > > > % unmount /export/home/1 > > % tunefs -q user /export/home/1 > > % fsck -fy /export/home/1 > > ... > > > USER QUOTA MISMATCH FOR ID 0: 0/0 SHOULD BE 1791988/1794 > > > ALLOC? yes > > > USER QUOTA MISMATCH FOR ID 0: 0/0 SHOULD BE 0/0 > > > ALLOC? yes > > > fsck: /dev/home/rtheory1: Segmentation fault > > > > This is on Sparc64. I'll provide more data tomorrow, assuming > > I'll find time to point gdb at a -g binary and the core dump. > > it should not try to allocate/fix entries for the same uid twice. > Also, "0/0 SHOULD BE 0/0" looks wrong. It would be interesting > to see if an entry got really added for id 0 twice, of if the second > id is the result of some corruption.
Sounds like a little-endian bug, referencing a value through a pointer of the wrong size so you only load the top zeros instead of the low significant bits. Eduardo
