search for: flex_bg

...es that is what I really meant. My experience with filesystems is mainly from CPM/BDOS, where "directory" and block mapping are essentially synonymous. And now I understand about the timing. Makes sense when you describe it that way. My system is ext4, although I doubt that I used "flex_bg" option, since this was first created awhile back. I did try to run e4defrag. It simply said that no defrag was needed. So, now I'm only left in need of a work-around. Perhaps a way to have the system load the bitmaps at boot time in the background? It would need to be done in such a way...

...rnal, ext2 can't mount feature needs_recovery. Despite from this, they are pretty much identical. The fs driver called ext4 supports some new features, the prominent (i.e. documented) ones are: extent (don't store cluster pointers but instead cluster ranges - saving space for large files), flex_bg (drop the constraint, that group meta data shall be stored in it's own group, thus allowing to virtually create bigger 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...

Hello, I have a production script that do read operations to a lot of small files. I read that one can gain performance boost with small files by using a loop device on top of Lustre. So a created 500 GB file striped across all of my OSTs(which are 8). I formatted the file with ext2 fs, and mounted it on a client. Just for the sake of testing a simple bash script finds all files with a given file

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.

...y better job of finding contiguous free space and avoid loading bitmaps that do not have enough space, but the physics of seeking to read bitmaps is still the same. If you format a new filesystem as ext4 (as opposed to just mounting the existing filesystem as ext4) you can use a new feature "flex_bg" that locates the block and inode bitmaps together so that they can be read without so much seeking. You'd need a spare disk to format and copy the data over to. Using ext4 is also more resistant to fragmentation over time. Cheers, Andreas > Any suggestions, tips, etc. greatly appre...

...{ + if (filetype) + strncat (features, ",filetype", 9); + else + strncat (features, ",^filetype", 10); + } + } + if (optargs_bitmask & GUESTFS_MKE2FS_FLEXBG_BITMASK) { + if (feature == 0) { + if (flexbg) + strncat (features, "flex_bg", 7); + else + strncat (features, "^flex_bg", 8); + feature++; + } else { + if (flexbg) + strncat (features, ",flex_bg", 8); + else + strncat (features, ",^flex_bg", 9); + } + } + if (optargs_bitmask & GUESTFS_M...

I asked about this a while back. It seems that this problem is getting much worse. The problem/issue: there is a very long delay when my system does a write to the filesystem. The delay now is over 5 minutes (yes: minutes). This only happens on the first write after booting up the system, and only for large files - 1GB or more. This can be a serious problem since all access to any hard disk is

...18.17t 134.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

The stripe and stride options do two things: - shift block and inode bitmaps in each group to be on different disks - align the block allocation to the stripe and stride boundaries to avoid read-modify-write in RAID The first one is irrelevant if the flex_bg option is used, since it already packs the bitmaps together and achieves the same effect. The second is meaningless for RAID-1 since writes go to every disk and there is no parity or read-modify-write for small or unaligned writes. Cheers, Andreas > On Mar 7, 2014, at 19:23, Martin T <m4...

...nt > feature needs_recovery. Despite from this, they are pretty much identical. > > The fs driver called ext4 supports some new features, the prominent > (i.e. documented) ones are: extent (don't store cluster pointers but > instead cluster ranges - saving space for large files), flex_bg > (drop the constraint, that group meta data shall be stored in it's own > group, thus allowing to virtually create bigger 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 m...

...> > > 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 /redirectedFolders/Users/' does seem to give me the > "User...

Andreas, why is it relevant only in case of RAID5 or RAID6? regards, Martin On Fri, Mar 7, 2014 at 5:57 PM, Andreas Dilger <adilger@dilger.ca> wrote: > Note that stride and stripe width only make sense for RAI-5/6 arrays. > For RAID-1 it doesn't really matter. > > Cheers, Andreas > >> On Mar 6, 2014, at 13:46, Martin T <m4rtntns@gmail.com> wrote: >>

...usershare path = restrict anonymous = 2 [c$] path = /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.

...POSIX ALCs enabled, so am using a > 4.4.52 kernel built from source with the EspressoBin required updates > and POSIX ACLs (ext3 and ext4) enabled. > > tune2fs reports > 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 Much the same as my computer. > > > I've seen the reports that this works on Ubuntu 18.04, which is why I > have spent 5 weeks trying.? I've been tracing ev...

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: ------

...lesystem volume name: <none> Last 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:...

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 >

...m 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 /redirectedFolders/Users/' does seem to gi...