search for: sparse_sup

...e2fsprogs-1.27-1. On the 2.6 desktop it's e2fsprogs-1.35-12. I built e2fsprogs-1.38 for the desktop and the result was the same. I used dumpe2fs on the working and non-working filesystems and found that the newer FS has different features: < Filesystem features: has_journal filetype sparse_super > Filesystem features: has_journal resize_inode filetype sparse_super After writing to a new FS on the desktop a further feature is added, < Filesystem features: has_journal resize_inode filetype sparse_super > Filesystem features: has_journal ext_attr resize_inode fil...

...ead the man page). It's most likely the > dir_index feature... > Thanks Peter for the prod in the right direction. A v4 filesystem shows these features # tune2fs -l /dev/sda1 | grep features Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file A v3 filesystem has these features # tune2fs -l /dev/sda5 | grep features Filesystem features: has_journal filetype needs_recovery sparse_super Tunes2fs from v4.2 can be used to remove "has_journal filetype dir_index sparse_super" Booted into rescue mode with a v4.2...

...stripe size and read/write/cache policies at a later stage, but any advice on selecting the appropriate parameters is greatly appreciated. I considered other file systems but have chosen ext3 for various reasons not discussed here. When creating the file system I used the following options: -O sparse_super -O dir_index -R stride=8 -O sparse_super because I don't want to waste too much space -O dir_index because this is supposed to help file listing performance with Samba shares -R stride=8 because of the 32kb stripe size (4kb*8=32kb) The next stage in my plan is to optimise file system perfor...

When I first installed ext3, it worked as expected. After a crash, journals would be played, and no fsck. Now, every crash causes an fsck, just like it were a regular ext2, even though / has a journal and is being mounted as ext3. Some fs info for / Filesystem features: has_journal filetype sparse_super Filesystem state: not clean Errors behavior: Continue Some fs info for /home, which seems to be working OK: Filesystem features: has_journal filetype needs_recovery sparse_super Filesystem state: clean Errors behavior: Continue Maybe related to not having...

...message: permission denied while trying to create journal file There is a .journal file in /: [root@monster log]# ls -l /.journal -rw------- 1 root root 33554432 Sep 29 10:21 /.journal But dumpe2fs doesn't seem to know about it: Filesystem features: filetype sparse_super What to do?

...) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: a4b7ee96-4aa9-4312-9ec9-91059539ece5 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal resize_inode dir_index filetype 64bit sparse_super large_file Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 393216000 Block count: 786432000 Reserved block count: 39321600 Free blocks: 774032395 Free inodes...

I created a filesystem as follows: mke2fs -j -O dir_index -O sparse_super -T largefile /dev/drbd/6 Here's the the output from df Filesystem Size Used Avail Use% /dev/drbd/6 475G 33M 452G 1% It seems that ext3 has taken 23 GB, which is about 5% of the total disk size, for itself. Is that right? If that is, indeed, the case, why does d...

...ould allow to recover the data? Probably there is some specific options for the recovery ralated with journaling in ext3? I have used debugfs, it produced following, if it helps: debugfs: open -f -w /dev/sdb1 debugfs: features Filesystem features: has_journal resize_inode filetype needs_recovery sparse_super large_file thanks, Dmitry

...Here's the system information and command line used to create the filesystem : SuSE SLES9 2 , kernel 2.6.5 ada718-5:/ # rpm -qa | grep e2fs e2fsprogs-1.36-6.2 ----------------------------------------- mke2fs -O journal_dev /dev/mapper/home_jou_vol_grp-home_jou 400000 mke2fs -E stride=16 -O sparse_super,dir_index -j -J device=/dev/mapper/home_jou_vol_grp-home_jou /dev/mapper/home_vol_grp-home Any ideas? Thanks in advance, -- Franco Bladilo Linux/HPCC Administrator Research Computing Support Group Rice University bladilo at rice.edu

....27 (8-Mar-2002) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 80307f32-6acd-4856-8ce4-63044f30d057 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super large_file Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 122109952 Block count: 244197920 Reserved block count: 12209896 [....] Can I run any other diagnostics to find out more about RAID...

...is works something like a cache for another app and I can't redesign the way it distributes files into disk due to the other app requirements). The filesystem I use is ext3 with teh following options enabled: Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file Is there any way to improve performance in ext3? Would you suggest another FS for this situation (this is a prodution server, so I need a stable one) ? Thanks in advance (and please excuse my bad english). _________________________________________________________________ Connect to...

...25 (20-Sep-2001) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: b1ceff3e-caca-4635-b6aa-3712b63f8917 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 1198208 Block count: 2395693 Reserved block count: 119784 Free blocks: 2315027 Free inodes: 1183124 First block: 0 B...

Does Fsync of a file on a ext3 fs mounted with "ordered" option(the default) result in flush the dirty data buffers in the fs that correspond to previous transactions. In other words, if I keep writing to file1 (lots of data), log something to file2, keep fsyncing file2 after every write - does this mean file1 data would be committed by fsyncs on file2. Please copy me on your replies

...from RHEL3 to RHEL4. I had to install from c0d0p6 so partition could not be reformated during install. Thanks, Mindaugas # dumpe2fs /dev/cciss/c0d0p1 | fgrep features dumpe2fs 1.35 (28-Feb-2004) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super # dumpe2fs /dev/cciss/c0d0p6 | fgrep features dumpe2fs 1.35 (28-Feb-2004) Filesystem features: has_journal filetype needs_recovery sparse_super large_file

...g tune2fs. I'm running a 2.4.10 kernel with ext3 support, but the partition is not mounted ext3. In fact the journal feature is missing from the superblock: # cat /proc/filesystems | grep ext ext3 ext2 # tune2fs -l /dev/hda6 | grep features Filesystem features: filetype sparse_super # ls -l /.journal -rw------- 1 root root 33554432 Oct 21 20:19 /.journal So when I try to add the journalling feature to the superblock, it refuses: # tune2fs -j /dev/hda6 tune2fs 1.25 (20-Sep-2001) Creating journal inode: tune2fs: Permission denied while trying to create jour...

...ode) + strncat (features, ",resize_inode", 13); + else + strncat (features, ",^resize_inode", 14); + } + } + if (optargs_bitmask & GUESTFS_MKE2FS_SPARSESUPER_BITMASK) { + if (feature == 0) { + if (sparsesuper) + strncat (features, "sparse_super", 12); + else + strncat (features, "^sparse_super", 13); + feature++; + } else { + if (sparsesuper) + strncat (features, ",sparse_super", 13); + else + strncat (features, ",^sparse_super", 14); + } + } + if (optar...

Hi, I have two 3TB (hardware RAID-5) ext3 filesystems and recently added 1TB to each. I resized each filesystem and e2fsck -f reports that both are fine. However, when I look at the ext3 parameters with tune2fs -l one seems to have some parameters that the other one doesn't. In particular, one has: "Reserved GDT blocks", "Filesystem created", "Default directory

...nal, as I could not find any option to e2fsck to tell it to skip applying (and reading) the journal, I set the filesystem festure 'has_jounal' off, using debugfs: # debugfs -b4096 -s32768 -w /dev/hda11 debugfs 1.39 (29-May-2006) debugfs: feature -has_journal Filesystem features: filetype sparse_super debugfs: show_super_stats -h Filesystem volume name: /var Last mounted on: <not available> Filesystem UUID: 2e8920a2-0460-4a87-b729-af812327fce7 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: filetype sparse_super Defau...

...Filesystem volume name: /store1 Last mounted on: <not available> Filesystem UUID: 2368a03d-f21f-4c5e-b12a-cbd2c726237c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode filetype needs_recovery sparse_super large_file Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 97681408 Block count: 195354408 Reserved block count: 9767720 Free blocks: 22200635 Free inodes:...

...002) /dev/hda1: Can't read an inode bitmap while reading inode bitmap debugfs: open -c /dev/hda1 /dev/hda1: catastrophic mode - not reading inode or group bitmaps debugfs: stat <8> stat: Invalid argument while reading inode 8 debugfs: stats ... Filesystem features: has_journal filetype sparse_super Filesystem state: clean with errors ... Directories: 1122431 Group 0: block bitmap at 33188, inode bitmap at 19132, inode table at 1027802808 6794 free blocks, 15870 free inodes, 1720 used directories Group 1: block bitmap at 0, inode bitmap at 0, inode table at 3...