Quoting Theodore Ts'o (2014-09-02 15:50:14) > On Tue, Sep 02, 2014 at 01:59:34PM +0200, 4win...@informatik.uni-hamburg.de > wrote: > > Package: e2fsprogs > > Version: 1.42.12-1 > > Severity: normal > > Tags: patch > > > > Dear Maintainer, > > > > e2fsck accesses the field osd2.linux2.l_i_file_acl_high field without > > checking that the filesystem is indeed created for Linux. This leads > > to e2fsck constantly complaining about certain nodes: > > > > i_file_acl_hi for inode XXX (/dev/console) is 32, should be zero. > > > > By "correcting" this problem, e2fsck clobbers the field > > osd2.hurd2.h_i_mode_high. > > Interesting; is this a field that hurd has recently started using? > (We've had this check in e2fsck for 4 years, when we added support for > 64-bit file systems.)
No. It has been used at least since 1996. Amazingly this seems to have no ill effect other than to make e2fsck complain constantly. > If so, for what? It seems to store more mode bits. > And did the hurd developer who started using this field realize he > has foreclosed the use of file systems larger than 16TB on the hurd? Probably not. We can switch to the Linux on-disk format once we can store all Hurdish stuff in extended attributes though. Thanks, Justus -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
