similar to: Ghost 8.0 Clone Filesystem with ext3 (remove resize_inode and ext_attr features)

Peter Kjellstr?m wrote: > On Monday 23 January 2006 16:46, Plant, Dean wrote: >> I need to downgrade a system from Centos x4.2 to v3.6 (x86) due to >> performance problems with Arkeia Network Backup and AIT-4 tape >> drives. The backup database is stored on a v4.2 created ext3 >> partition. When accessing this partition after the downgrade, Centos >> complains on

Hi, I'm using ext3 filesystems in embedded devices (storage is on 512Mb or 1Gb CF cards). A typical development cycle would see the filesystem created on the desktop PC running linux 2.4 (eg. RedHat 9). The CF card would be installed in the hardware and linux 2.4 (eg. Montavista Pro 3.1, on PPC) would boot from the CF. Recently I tried a linux 2.6 desktop (CentOS) for the same task and

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

Hi, Fedora Core ext3 file systems newbie questions: Just interested in the Linux ext3 features but got confused with "large_file" and "ext_attr". First, what's the "large_file" feature REALLY means? For file systems created with same commands and options some file systems have it on while some not. It is said that the feature is automatic -- If there is a

I've been thinking recently that we should re-enable DIR_INDEX in mke2fs 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

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

Hey, I have two identical machines setup with a RAID 5 array. One of them is used for failovers and data from the master is synced everyday using rsync to the failover machine. The data on this disks are usually intranet KB's, DB's etc.. The RAID 5 arrays are formatted using the default options i,e mkfs.ext3 /dev/Xda. The RAID controller is 3ware escalade and each disk member in the RAID

On Sun, 17 Dec 2023 20:16:23 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > on Sun Dec 17 12:15:28 2023 Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > > On Sun, 17 Dec 2023 11:50:18 -0500 > > Mark Foley via samba <samba at lists.samba.org> wrote: > > > > > > Spindles7, Thanks. my cloning the

Hello guys, I have some difficulties to understand what really are the numbers behing "df" and tune2fs. You'll find the output of tune2fs and df below, on which my maths are based. Here are my maths: A tune2fs on an ext3 FS tell me the FS size is 3284992 block large. It also tell me that the size of one block is 4096 (bytes if I'm not wrong?). So my maths tell me that the disk

Hi all, I want to setup a linux workstation with FC4 and 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

Hi, Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal using the

I've just made e2fsprogs 1.36-rc1 available on Sourceforge: http://sourceforge.net/project/showfiles.php?group_id=2406&package_id=2383&release_id=295092 Fedora Core 3 users will be strongly encouraged to upgrade to e2fsprogs 1.36, since it has numerous bug fixes to some of the Fedora-specific enhancements to e2fsprogs --- in particular, supporting on-line resizing feature using the

On 9/16/13 5:16 AM, Nicolas Michel wrote: > Hello guys, > > I have some difficulties to understand what really are the numbers > behing "df" and tune2fs. You'll find the output of tune2fs and df > below, on which my maths are based. > > Here are my maths: > > A tune2fs on an ext3 FS tell me the FS size is 3284992 block large. It > also tell me that

Thanks for you help. I also tried adding some other informations as you suggest: I can also take into account: - "Reserved block count: XXXXXXX" from tune2fs that gives me the number of blocks reserved for root - Reserved GDT blocks: XXX But I didn't thought about the FS journal. How can I gather information about it? (it's size and any other information?) 2013/9/16

On Dec 18 03:22:32 2023 Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sun, 17 Dec 2023 20:16:23 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > on Sun Dec 17 12:15:28 2023 Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > > On Sun, 17 Dec 2023 11:50:18 -0500 > > > Mark

Hello, I have 2 boxes with 1.5TB storage with ext3 fs, and the kernel is 2.6.11.8. I'm using E2fsprogs 1.37 for FS creation. And, Filesystem revision #: 1 (dynamic) There are 2 scenarios: 1. All SATA drives, RAID5 2. All PATA drives, RAID5 and wrapped in log volumes. I'm having lots of issues with fsck. I did search, but somehow not getting the right information. needs_recovery

On 9/16/13 9:44 AM, Nicolas Michel wrote: > Thanks for you help. I also tried adding some other informations as you suggest: > I can also take into account: > - "Reserved block count: XXXXXXX" from tune2fs that gives me the > number of blocks reserved for root > - Reserved GDT blocks: XXX > > But I didn't thought about the FS journal. How can I gather

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 3125's inode table at 102400545 conflicts with

Hello, How to upgrade existing ext3 partition to new features? Moved 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

On 8/17/14, 12:28 PM, Roland Olbricht wrote: > Hello everybody, > > first of all thank you the development of Ext2/3/4. It works like a > charm and makes it possible to base applications on it. > However, "df" says: > > Filesystem 1K-blocks Used Available Use% Mounted on > ... > /dev/sdc 468346644 409888536 35015532 93% /opt/ssd >