"Sparhawk" <[EMAIL PROTECTED]> wrote in news:[EMAIL PROTECTED]:
> I can confirm that Redhat Enterprise Linux 4.0 suffers from this same > problem as well. After completing the steps outlined below you > receive the following msg upon rebooting to LFS. > > Filesystem contains large files, but lacks LARGE_FILE flag in > superblock. > > You are then instructed to run e2fsck manually without -a or -p > options. When you do this from redhat it fixes the filesystem by > re-adding the large_file option back to the filesystem. > > Should this version of redhat be added to the bug as well? > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Gerard > Beekmans > Sent: Tuesday, February 22, 2005 11:20 AM > To: LFS Support List > Subject: Re: File System Issues during bootup > > On February 21, 2005 08:43 pm, Steve Crosby wrote: >> for example, to remove large_file and resize_inode from /dev/sdc1 >> >> echo "features -resize_inode" | debugfs -w -f- /dev/sdc1 >> echo "features -large_file" | debugfs -w -f- /dev/sdc1 >> e2fsck -p /dev/sdc1 > > Bad FC3, bad. Wow that's ugly. Rumor has it that e2fsprogs-1.36 may > have these > new features built in as well. Maybe not. > > I'll add your latest notes to the bugzilla bug and we'll have to do a > more thorough investigation and consider our options. > although it's not documented that I could see quickly, the large_file capability appears to already be in e2fsprogs upstream - so you only need to remove the resize_inode capability, which the e2fsprogs from LFS 6.0 and earlier can't understand. An alternative is to use version 1.36 of e2fsprogs in LFS, which seems to have implemented the resize_inode capability. -- - Steve Crosby -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
