search for: resize_inod

...nd with all the partitions (except for /boot) under LVM to be able to resize them in future. I don't need online resizing, I can shutdown the system and reboot with the rescuecd when needed. I have done some test on this configuration and I have sverals doubts: If i format a partition with the resize_inode feature enabled and I resize it offline with resize2fs all is ok until I reach (in a single step or in several step) 1000*(Original Size). When i extend a partition over this size I receive a couple of error when I launch fsck.ext3 and the resize_inode feature disappears. If I format a partition...

I've Found a page with interesing discussion about images backup http://forums.fedoraforum.org/archive/index.php/t-28255.html This give a "dirty" solucion for remove special thing of ext3 (Selinux remove resize_inode and ext_attr features) witch cause the error in ghost. I hope somebody help with the problem of norton ghost and clone centos 4. :) ----------- sfabkk 2005-07-11, 04:53 AM PDT Solution to using Ghost 8 with Core 3 and 4 Good news : It can be done Bad News : You have to turn off SELinux Foreve...

...ke2fs by default. When it first came out, we had done this and were bitten by a few bugs in the code. However, this code has been in heavy use for several thousand filesystem years in Lustre, if not elsewhere, and I'm inclined to think it is pretty safe these days. Likewise, RHEL/FC have had RESIZE_INODE as a standard feature for a good time now, and this should probably be merged into stock e2fsprogs. Comments? Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc.

....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 filetype sparse_super I'm not convinced the features ar...

.../dev/sda5" and > toggle features too (read 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_sup...

...generally built for these platforms. For people who used resize2fs on Fedora Core 3 on a filesystem created using mke2fs from FC3, and trashed their filesystem, it will be possible to recover using the following procedure after installing e2fsprogs 1.36: debugfs -w /dev/hdXXX -R "features ^resize_inode" e2fsck -f /dev/hdXXX This will remove the resize_inode feature, and correct the filesystem corruption. If you would like to use on-line resizing, you can then run ext2prepare, which should restore the resize_inode correctly. I'm asking people who are willing to be guinea pigs to down...

...2fs -h info: dumpe2fs 1.39 (29-May-2006) 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 bloc...

...s.. Is there any way, any tool that would 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

...my application gets slower and slower (the app 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). ______________________________...

Hi, first of all, apologies if this isn't the right mailing list but it was the best I could find. If you know a better mailing list, please tell me. Today I tried to defrag one of my filesystems. It's a 3.5T large filesystem that has 6 software-raids in the bottom and then merged together using lvm. I was running ext3 but removed the journal flag with thor:~# tune2fs -O ^has_journal

Hi, I'm about to roll out a whole bunch of Redhat Enterprise 4 workstations and have run into problems cloning from the original. Normally I would use ghost (v7.5) because it does a nice job when cloning to a different sized disk.Unfortunately it comes up with read error 29004. Looking around it seems that Symantec don't support Fedora Core 3 (with Ghost v.8 - don't know if v.9 works

...{ + if (quota) + strncat (features, ",quota", 6); + else + strncat (features, ",^quota", 7); + } + } + if (optargs_bitmask & GUESTFS_MKE2FS_RESIZEINODE_BITMASK) { + if (feature == 0) { + if (resizeinode) + strncat (features, "resize_inode", 12); + else + strncat (features, "^resize_inode", 13); + feature++; + } else { + if (resizeinode) + strncat (features, ",resize_inode", 13); + else + strncat (features, ",^resize_inode", 14); + } + } + if (optarg...

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

...dev/sda1 dumpe2fs 1.35 (28-Feb-2004) 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:...

Hi, I've installed a few Fedora Core 4 and Fedora Core 5 recently, and found that the new ext3 file systems created with new mkfs.ext3(1.38+) has one more field than EXT3 created with old mkfs.ext3(1.34-), even the latter's dir_index feature was turned on and file systems were upgraded with "e2fsck -y -f -D" command. I have three questions thereafter: 1) what does the

...lv tune2fs 1.41.9 (22-Aug-2009) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 4e5bea3e-3e61-4fc8-9676-e5177522911c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: unsigned_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 822544 Block count:...

...ount option "commit=<number of seconds>"). So started trying these settings. I didnt manage to determine the size of the journal of an already existing filesystem. tunefs tells me the inode: ~# tune2fs -l /dev/vg0/lvol0 | grep -i journal Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file Journal inode: 8 Journal backup: inode blocks Is there a way to get the size of the journal? And how do I find out how much of the journal is used? Or how often a journal flush actually happens? Or whether the jou...

...ection of > > > your smb.conf file:" > > > > > > I do have a "system that supports NFS4 ACLs" > > > > What filesystem is that ? > > ext4: > > # tune2fs -l /dev/sda3 | grep attr > Filesystem features: has_journal ext_attr resize_inode dir_index > filetype needs_recovery extent 64bit flex_bg sparse_super large_file > huge_file dir_nlink extra_isize metadata_csum Default mount options: > user_xattr acl > > I believe this means I'm good with NFS4 ACLs. If not, please advise. > Doing 'getfacl /redirecte...

...lume name: <none> >> Last mounted on: <not available> >> Filesystem UUID: 4e5bea3e-3e61-4fc8-9676-e5177522911c >> Filesystem magic number: 0xEF53 >> Filesystem revision #: 1 (dynamic) >> Filesystem features: has_journal ext_attr resize_inode dir_index >> filetype needs_recovery sparse_super large_file >> Filesystem flags: unsigned_directory_hash >> Default mount options: (none) >> Filesystem state: clean >> Errors behavior: Continue >> Filesystem OS type: Linux >...

...isk size ? I got round this by re-starting the guest, but it would be better if there is some way to force the guest to see the new size. The second problem was that parted gave an error : Error: Filesystem has an incompatible feature enable. Some reading showed that this was caused by the "resize_inode" feature on the file system. I removed this feature using debugfs, and rans fsck, but parted still gave the same error: Error: Filesystem has an incompatible feature enable. I would like some advice on how this is supposed to be done. Thanks in advance. Chandana