search for: huge_file

...e a file, or move it from one folder to another. Current behaviour (please correct me if I am wrong) is for wget to see this as a 'delete' and an 'add'. The 'add' results in a complete retransfer of the file. This could be optimized. For example, if I move local file 'huge_file' to 'old/huge_file', a complete retransfer happens to the remote end of the 'new' file. My proposed implementation is that out the outset, during generation of file lists of local and remote, the checksums of entire files be computed (already happening with --checksum, I belie...

...lvm2 a-?? 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

...stem 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 > Properties > Security" se...

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

...; 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 every > report/tutorial/blog/video I c...

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

...> 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: 7324218 Reserved block coun...

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 >

...> > > > 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 > Properti...

...t mounted on: /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 Reserve...

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,

...name: /dev/sda1 logical name: /boot version: 1.0 serial: 52f28da4-4564-4bb6-8b66-b2778a76b5c6 size: 500MiB capacity: 500MiB capabilities: primary bootable journaled extended_attributes large_files huge_files dir_nlink extents ext4 ext2 initialized configuration: created=2012-11-09 23:06:43 filesystem=ext4 lastmountpoint=/boot modified=2013-01-29 11:22:20 mount.fstype=ext4 mount.options=rw,relatime,data=ordered mounted=2013-01-29 11:19:39 state=mounted *-volume:1...

...for the bad block inode to make sure it looks sane before trusting it, to avoid causing more harm than good to the file system. E2fsck now returns additional status bits in its exit code if it aborts early in the e2fsck run. E2fsck now correctly calculates the maximum file size in the case of the huge_file file system feature enabled without extents. The mke2fs and e2fsck programs now tries to use the punch hole command as a "discard" when operating on normal files. The e2image program now supports the qcow2 format, which is a more efficient way of capturing file system dumps. Mke2fs now...

...m volume name: <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: 143862272...

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/

I'm trying to configure an SoC system as an AD DC on Ubuntu 18.04. I was successful on Ubuntu 16.04 a couple of years ago, and the script I used to configure the system from first boot to provisioned fails on 18.04 and 16.04. The failure is thus: Setting up self join set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_NOT_SUPPORTED. ERROR(runtime): uncaught exception - (-1073741637,