Hi Guys, When I try to create an ext3 journal on a new fs, I receive the following error. This is all under Kernel v2.4.17 and e2fs tools v1.25: File size limit exceeded Running e2fsck on it afterwords gives: e2fsck -y /dev/sdc1 e2fsck 1.25 (20-Sep-2001) Superblock has a bad ext3 journal (inode 8). Clear? yes *** ext3 journal has been deleted - filesystem is now ext2 only *** Superblock doesn't have has_journal flag, but has ext3 journal inode. Clear? yes /dev/sdc1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Journal inode is not in use, but contains data. Clear? yes File size limit exceeded
Hi, On Thu, Feb 28, 2002 at 08:26:13AM +1100, Adam Cassar wrote:> Hi Guys, > > When I try to create an ext3 journal on a new fs, I receive the > following error. This is all under Kernel v2.4.17 and e2fs tools v1.25: > > File size limit exceededYou have probably got user limits running on the account: type "ulimit -a" under bash ("limit" on csh) to see the limits in force. In particular, you'll probably see a max file size limit. That's a local login shell configuration issue. --Stephen
Possibly Parallel Threads
- Problem in e2fsck ? read error in journal inode
- EXT3: failed to claim external journal device.
- [PATCH 0/8] extlinux: support unmounted ext2/3/4 filesystem
- [PATCH 0/8] extlinux: support unmounted ext2/3/4 filesystem
- [PATCH 0/9] linux/syslinux: support ext2/3/4 device