search for: uninit_bg

Hi all, I issued the commands on a single disk system: with two partitions / is linux sda1 and /home is sda3 yum -y update yum -y install e4fsprogs reboot umount /home tune2fs -O extents,uninit_bg,dir_index /dev/sda3 e2fsck -yfDC0 /dev/sda3 That worked just fine. I then had a different system that is software raid. where / is linux and md0 and /home is md1 yum -y update yum -y install e4fsprogs reboot umount /home tune2fs -O extents,uninit_bg,dir_index /dev/md1 at this point...

...arsesuper) + strncat (features, ",sparse_super", 13); + else + strncat (features, ",^sparse_super", 14); + } + } + if (optargs_bitmask & GUESTFS_MKE2FS_UNINITBG_BITMASK) { + if (feature == 0) { + if (uninitbg) + strncat (features, "uninit_bg", 9); + else + strncat (features, "^uninit_bg", 10); + feature++; + } else { + if (uninitbg) + strncat (features, ",uninit_bg", 10); + else + strncat (features, ",^uninit_bg", 11); + } + } + + if (feature != 0) { +...

...34.12g # lvs ? LV??? VG????? Attr?? LSize? Origin Snap%? Move Log Copy%? Convert ? data1 vgRAID6 -wi-ao 18.00t and the cryptsetup resize worked like a charm. I ran? e2fsck before the resize which pass sucessfully. I added ext4 = { ??????????????? features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize ??????????????? auto_64-bit_support = 1 ## ADDED THIS ??????????????? inode_size = 256 ??????? } to /etc/mke2fs.conf and run resize2fs and got the same error

What will be the correct way to migrate ext3 to ext4 going from 5.5 to 5.6? Will something after the update ask if you want to migrate the file systems? Looking forward to some file system speed ups with large files. Thanks Jerry

...groups. Probably you can mke2fs one file system with flex_bg, then remove the feature flag and perfecly mount and use it with ext2 / ext3, however, e2fsck may get cracy on that setup - but I don't see, why the file system drivers should get a problem with that - anyways, I didn't test it), uninit_bg (speeds up mke2fs by skipping the "overwrite all bitmaps and inode tables with zeros" step). Regards, Bodo

I hope this is the right list. I have created an ext2 filesystem and removed the dir_index feature. I don't know if this kind of experimentation is going to help me learn something about filesystems or not. Well what is dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I remove? Htree. I guess it can always be put back and it's on an experimental filesystem.

...smbshare read only = No From dumpe2fs, these are the filesystem features of the destination PC: Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Default mount options: user_xattr acl What do you think? Cesare.

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

Yes indeed it is probably what's going on. what filesystem are you using and what are the mount options? ? Original Message ? From: lists at bago.org Sent: November 22, 2017 4:26 PM To: gluster-users at gluster.org Subject: [Gluster-users] error "Not able to add to index" in brick logs in my /var/log/gluster/bricks/mybrick-path.log I get thousands of those errors: ------

...reformat --index=35 \ --mkfsoptions="-i 2000000" --reformat --mountfsoptions="errors=remount-ro,extents,mballoc,stripe=256" /dev/sdc The UUID here is taken from the /etc/fstab, where the entry has been commented out until we are ready to again use the volume 310 tune2fs -O uninit_bg -m 1 -U 02bcb3d2-ad48-4992-ba71-7b48787defea /dev/sdc 311 e2fsck -fy /dev/sdc 312 mount -t ldiskfs /dev/sdc /mnt/ost Copy back all identifiers so that the volume can continue from where it was left off 315 cd /root/reformat/sdc 316 cp -v /mnt/ost/CONFIGS/mountdata mountdata.new2...

1. ext4 mke2fs -b 4096 -m 5 -t ext4 -O^uninit_bg -r 1 -v /dev/sdb1 sdparm --command=sync /dev/sdb 2. 150G 3. gdisk /dev/sdb x a 2 w y sdparm --command=sync /dev/sdb 4. mount /dev/sdb1 /mnt/sdb1 cd /mnt/sdb1 extlinux -i /mnt/sdb1/boot umount /mnt/sdb1 sync;sync;sync sdparm --command=sync /dev/sdb cat gptmbr.bin >/dev/sdb1 sync;sync;sync sdparm...

...mounted on: / Filesystem UUID: 88e70e1b-4c45-4e7e-931f-9e97d7257ee8 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 1831424 Block count: 7324218 Reserved block count: 366...

in my /var/log/gluster/bricks/mybrick-path.log I get thousands of those errors: ------ [2017-11-22 21:06:23.768354] E [MSGID: 138003] [index.c:624:index_link_to_base] 0-sharedvol-index: /home/sharedvol/.glusterfs/indices/xattrop/0b852dad-b332-4bfe-a38b-976729ee46a2: Not able to add to index [Troppi collegamenti] The message "E [MSGID: 138003] [index.c:624:index_link_to_base]

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 >

...n: /opt/ssd Filesystem UUID: 75d6aae6-1746-4260-994b-148dfdb5af95 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 29310976 Block count: 117212886 Reserved block cou...

...u can > mke2fs one file system with flex_bg, then remove the feature flag and > perfecly mount and use it with ext2 / ext3, however, e2fsck may get cracy > on that setup - but I don't see, why the file system drivers should get a > problem with that - anyways, I didn't test it), uninit_bg (speeds up > mke2fs by skipping the "overwrite all bitmaps and inode tables with > zeros" step). > > Regards, Bodo Yes all those features. I would like to know what they mean. There are mount options, ext4 features, ext3 features and some are directly related to the jou...

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, now I have the first time where I need more information to understand the behaviour of a ext4 installation on a 480 GB harddisk. It holds a database with a size of 355 GB, as said by "du -m": ... 355263 /opt/ssd However,

...related to the other flush-btrfs-1 thread. plenty of diskspace is free: /dev/mapper/cruor-build 97G 68G 27G 73% /opt/build It always hangs when openwrt builds the ext4 image and runs tune2fs on it. /opt/build/fahrenheit/openwrt/staging_dir/host/bin/tune2fs -O extents,uninit_bg,dir_index /opt/build/fahrenheit/openwrt/build_dir/linux-x86_kvm_guest/root.ext4 tune2fs 1.41.13 (13-Dec-2010) the processes can''t be killed. alt-sysctl-t does not show anything, nor is there a oops. I put the the openwrt config I''m using at https://gist.github.com/794593 , mayb...

...ame: <none> Last mounted on: /vz Filesystem UUID: 74a4ea8b-03ed-4e9c-ab01-8574517cd5af Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: not clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 359661568 Block count: 1438622720 Reserved...

We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS. I know there are different methods for formatting large disks but this one doesn't even seem to show up as a /dev/