search for: resize_inod

Displaying 20 results from an estimated 34 matches for "resize_inod".

Did you mean: resize_inode
2005 Jun 19
6
ext3 offline resizing
...ll 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...
2006 Mar 17
17
[RFC] mke2fs with DIR_INDEX, RESIZE_INODE by default
...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.
2005 Sep 20
2
ext3 incompatability between linux 2.4/ppc and linux 2.6/x86
....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 featur...
2006 Jan 26
1
Ext3 filesystem access after downgrade from v4.2 to v3.6 [SOLVED]
...t; 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 sp...
2007 Feb 17
7
Filesystem won''t mount because of "unsupported optional features (80)"
...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...
2005 Jan 07
0
e2fsprogs 1.36-rc1 released on SourceForge
...ly 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...
2006 Jul 26
7
data recovering in EXT3
...here 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
2010 Oct 04
19
EXT4 mount issue
Hi All, When a couple of EXT4 filesystems are mounted in a server I get the message Oct 1 18:49:42 sraid3 kernel: EXT4-fs (sdb): mounted filesystem without journal Oct 1 18:49:42 sraid3 kernel: EXT4-fs (sdc): mounted filesystem without journal in the system logs. My confusion is why are they mounted without a journal? They were both created with mkfs -t ext4 /dev/sdb mkfs -t ext4
2006 Oct 13
6
e2defrag - Unable to allocate buffer for inode priorities
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
2005 Jun 08
3
clone RHEL 4 ext3 partition
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
2009 Nov 29
1
Effects of Missing ext3 Parameters
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
2006 Dec 06
6
File size differences
...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:...
2006 May 07
1
Fedora Core 4 and FC5''s NEW EXT3 file system: "Reserved GDT 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
2007 Dec 11
2
Ext3 Performance Tuning - the journal
..."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...
2006 Oct 04
8
EXT3 and large directories
...fo: tune2fs 1.35 (28-Feb-2004) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 7cbda7aa-e8e7-4da1-9c7c-de45668e98f3 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 98304000 Block count: 196608000 Reserved block count: 9830...
2005 Feb 22
3
ext3 compatibility between 2.4 and 2.6 kernels
Hello-- We have a system where a central server formats removable hard disks, which are then booted in an embedded system running a highly modified RH9. The removable disks themselves contain boot, root, and data filesystems. The problem we''ve encountered after upgrading to FC3 / kernel 2.6 on the central server is that the 2.4 kernel in the embedded system cannot read the root
2004 Dec 09
5
resize2fs on LVM on MD raid on Fedora Core 3 - inode table conflicts in fsck
.../test debugfs 1.35 (28-Feb-2004) debugfs: stats Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: c037ef14-2db8-41ce-92bf-3b642a5bad55 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: resize_inode filetype sparse_super large_file Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 1310720 Block count: 2621440 Reserved block count: 131072 Free blocks: 257774...
2005 Feb 07
8
e2fsck errors after lvextend when trying to resize2fs
I found a thread that has almost the exact same symptoms as me, but didn''t seem to come to a resolution: https://listman.redhat.com/archives/ext3-users/2004-December/msg00018.html I have an LVM(2) array that I''ve just lvextend''d and want to resize2fs, but I can''t get through the e2fsck. I get these errors when fsck-ing: Group
2006 Nov 09
1
Ext3 - which blocksize for small files?
Hi, I want to use an ext3 Partition (~1TB) for Mail Storage, this means tons of small files. Has anyone recommendations about blocksize, inodes, etc. for mkfs.ext3 ? Thanks in advance, David -- View this message in context: http://www.nabble.com/Ext3----which-blocksize-for-small-files--tf2601442.html#a7257363 Sent from the Ext3 - User mailing list archive at Nabble.com.
2006 Feb 23
1
Ext3: Ordered : Fsync question
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