[SOLVED] Help needed to enable "large_file" using tune2fs

ZAMO · 12-05-2010, 10:49 PM

Hi ,

I want to enable the "large_file" option for a file system sda5. Though i got the option from "man tune2fs" , am unable to execute that.

Code:

#dumpe2fs -h /dev/sda5 |  grep "Filesystem features"
dumpe2fs 1.32 (09-Nov-2002)
Filesystem features:      has_journal filetype needs_recovery sparse_super

The following is not working , as i think am missing something here.

Code:

tune2fs -O[+]feature[,large_file] /dev/sda5

syg00 · 12-05-2010, 11:14 PM

You're reading too much into the syntax diagram - try "tune2fs -O large_file /dev/sda5"

gd2shoe · 12-05-2010, 11:19 PM

Note:

Quote:

man tune2fs
(Modern kernels set this feature automatically when a file > 2GB is created.)

Square brackets? (I assume you copied something incorrectly when posting. Otherwise, check here.)

try:

Code:

tune2fs -O +large_file /dev/sda5

ZAMO · 12-06-2010, 12:31 AM

Thanks syg00 and gd2shoe.

Am yet to try both options provided by you . I have a question before that . Is that ok to execute the tune2fs on a mounted File system ? If Yes, will that "large_file" support be available after a reboot ? Or do we need to run some commands to make that permanently .

Sorry to ask , as i don't have a test server for now.

Thanks
ZAMO

syg00 · 12-06-2010, 12:42 AM

Yes and yes. In fact if you don't do anything, and simply create a big file, the kernel will turn the option on for you.
Supposedly ....

BTW, both those commands do the same thing - do (just) one. The "+" is optional, as indicated by the square brackets in the manpage.

ZAMO · 12-06-2010, 12:52 AM

Hi syg00,

I raised this thread here , because when a log of around 2GB was created the system was unable to perform most functions . it failed to execute even simple commands as well with an error "File size limit exceeded" .

But even there , i wonder that one FS is enabled with large_file and others not . (provided no storage here and all in a singe HDD) . So i planned to enable large_file support manually .

syg00 · 12-06-2010, 12:58 AM

Might depend on level - I've never turned it on manually (other than just now), and I regularly download DVD isos (work and home). SLES11 disk2 (I think) was over 4 Gig.
Usually btrfs these days, but must have done it under ext[34] and had it turn on automagically.

gd2shoe · 12-06-2010, 01:44 AM

You might not have a "modern kernel". You could try updating.

Alternativly, this might be caused by a quota system of some kind. Try:

Code:

ulimit -a

(http://www.cyberciti.biz/faq/file-si...-and-solution/)

ZAMO · 12-06-2010, 01:59 AM

Thanks for the valuable inputs, but am unable to execute both option (i was suppose to use one):

Code:

#tune2fs -O large_file /dev/sda5
tune2fs 1.32 (09-Nov-2002)
Invalid filesystem option set: large_file
#tune2fs -O +large_file /dev/sda5
tune2fs 1.32 (09-Nov-2002)
Invalid filesystem option set: +large_file

Is not , i had executed "tune2fs -m" on a mounted partition? my system is a RHEL 3

Code:

$ uname -a
Linux zamo22  2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02 EST 2004 i686 i686 i386 GNU/Linux
$ cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon Update 4)
$ ulimit -a
core file size        (blocks, -c) 0
data seg size         (kbytes, -d) unlimited
file size             (blocks, -f) unlimited
max locked memory     (kbytes, -l) 4
max memory size       (kbytes, -m) unlimited
open files                    (-n) 1024
pipe size          (512 bytes, -p) 8
stack size            (kbytes, -s) 10240
cpu time             (seconds, -t) unlimited
max user processes            (-u) 7168
virtual memory        (kbytes, -v) unlimited

syg00 · 12-06-2010, 03:51 PM

2.4 ???. Erk - don't like your chances. I should have noticed the back-level version of tune2fs from your first post.

I doubt you can get a supported e2fsprogs that far back - RH usually rolls back what support it thinks users needs. My e2fsprogs is 1.41.10 for example (Fedora 13).

ZAMO · 12-06-2010, 05:07 PM

Thanks again . Finally i gave up in enabling this feature

chrism01 · 12-07-2010, 12:10 AM

Just an FYI, in case you don't already know: unless you want to pay the extra for 'Extended Support', RHEL 3 is now officially unsupported https://access.redhat.com/support/po...pdates/errata/