search for: large_fil

...ile larger than 2GB on a particular ext3 filesystem. I was under the (mistaken) impression that >2GB support went in before ext3 support, and all ext3 filesystems would therefore support >2GB files on ia32. So, I started poking around and found that some of my ext3 filesystems have the "large_file" feature flag set on them, and others do not. I cannot find a manpage for mke2fs anywhere that explains how to set this flag, either at creation time or afterwards. When I try something like "mke2fs -j -O large_file <dev>" mke2fs complains that it doesn't understand the ar...

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 large file then it is lit on otherwise...

...transfered. In a worst case the disk space is running out while this, even if there is enough disk space for a correct sync. (Of course, this happened me. :-) ) Here is an example: The local directory with a new hardlink to a file: $ ls -s1i rsync_test/ total 899960 3272008 449980 a_hardlink_to_large_file 3272008 449980 large_file The remote directory without the new hardlink: $ ls -s1i fake_remote/ total 449980 4088085 449980 large_file Rsyncing: $ rsync -aHPv rsync_test/ fake_remote building file list ... 3 files to consider ./ a_hardlink_to_large_file 460324864 100% 10.02MB/s 0:00:43 l...

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

...02) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 80307f32-6acd-4856-8ce4-63044f30d057 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super large_file Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 122109952 Block count: 244197920 Reserved block count: 12209896 [....] Can I run any other diagnostics to find out more about RAID drive? Is e2...

...thing like a cache for another app and I can't redesign the way it distributes files into disk due to the other app requirements). The filesystem I use is ext3 with teh following options enabled: Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file Is there any way to improve performance in ext3? Would you suggest another FS for this situation (this is a prodution server, so I need a stable one) ? Thanks in advance (and please excuse my bad english). _________________________________________________________________ Connect to the next ge...

...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 blocks: 774032395 Free inodes:...

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

...ournaldev) + strncat (features, ",journal_dev", 12); + else + strncat (features, ",^journal_dev", 13); + } + } + if (optargs_bitmask & GUESTFS_MKE2FS_LARGEFILE_BITMASK) { + if (feature == 0) { + if (largefile) + strncat (features, "large_file", 10); + else + strncat (features, "^large_file", 11); + feature++; + } else { + if (largefile) + strncat (features, ",large_file", 11); + else + strncat (features, ",^large_file", 12); + } + } + if (optargs_bitmas...

...lume 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: 22200635 Free inodes:...

...age). 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 sparse_super" Booted into rescue mode with a v4.2 cd and remov...

...t;none> Last mounted on: <not available> Filesystem UUID: 4e5bea3e-3e61-4fc8-9676-e5177522911c Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: unsigned_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 822544 Block count: 3284992 Reserved block count: 164249 Free blocks:...

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

...o 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 journal flushes happen because the commit interval has finish...

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

...I am not sure I follow. Let me be more specific. Say you have a trivial stream IO triggering reclaim to recycle clean page cache. This will invoke slab shrinkers as well. Do you really want to drop your batch of pages on each invocation? Doesn't that remove them very quickly? Just try to dd if=large_file of=/dev/null and see how your pages are disappearing. Shrinkers usually scale the number of objects they are going to reclaim based on the memory pressure (aka targer to be reclaimed). -- Michal Hocko SUSE Labs

...available> >> Filesystem UUID: 4e5bea3e-3e61-4fc8-9676-e5177522911c >> Filesystem magic number: 0xEF53 >> Filesystem revision #: 1 (dynamic) >> Filesystem features: has_journal ext_attr resize_inode dir_index >> filetype needs_recovery sparse_super large_file >> Filesystem flags: unsigned_directory_hash >> Default mount options: (none) >> Filesystem state: clean >> Errors behavior: Continue >> Filesystem OS type: Linux >> Inode count: 822544 >> Block count:...

...n: <not available> > Filesystem UUID: 4e5bea3e-3e61-4fc8-9676-e5177522911c > Filesystem magic number: 0xEF53 > Filesystem revision #: 1 (dynamic) > Filesystem features: has_journal ext_attr resize_inode dir_index > filetype needs_recovery sparse_super large_file > Filesystem flags: unsigned_directory_hash > Default mount options: (none) > Filesystem state: clean > Errors behavior: Continue > Filesystem OS type: Linux > Inode count: 822544 > Block count: 3284992 > Reserved...

...<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: 9830400 Free blocks: 31795332 Free inodes:...

...t;> Filesystem UUID: 4e5bea3e-3e61-4fc8-9676-e5177522911c >>> Filesystem magic number: 0xEF53 >>> Filesystem revision #: 1 (dynamic) >>> Filesystem features: has_journal ext_attr resize_inode dir_index >>> filetype needs_recovery sparse_super large_file >>> Filesystem flags: unsigned_directory_hash >>> Default mount options: (none) >>> Filesystem state: clean >>> Errors behavior: Continue >>> Filesystem OS type: Linux >>> Inode count: 822544 >&...