How to find out the parameters of an ext3 filesystem
Dan Track
dan.track at gmail.com
Wed Oct 14 15:26:15 UTC 2009
On Wed, Oct 14, 2009 at 4:18 PM, Ed Greshko <Ed.Greshko at greshko.com> wrote:
> Dan Track wrote:
>> On Wed, Oct 14, 2009 at 3:56 PM, Chris Adams <cmadams at hiwaay.net> wrote:
>>
>>> Once upon a time, Dan Track <dan.track at gmail.com> said:
>>>
>>>> I'd like to know the parameters of an ext3 filesystem i.e what
>>>> blocksize was used, inodes etc... Can someone please show me a command
>>>> I can use to find this information.
>>>>
>>> As root, "tune2fs -l <device>", where "<device>" is the block device
>>> that contains the filesystem (e.g. /dev/sda2, /dev/vg0/lv0, etc.).
>>> --
>>> Chris Adams <cmadams at hiwaay.net>
>>> Systems and Network Administrator - HiWAAY Internet Services
>>> I don't speak for anybody but myself - that's enough trouble.
>>>
>>>
>>
>> Great thanks. Can I ask one more question. I'm trying to put all the
>> information in the following website:
>> http://busybox.net/~aldot/mkfs_stride.html
>>
>> and it is asking me for the following: "number of filesystem blocks (in KiB)"
>>
> How does this question relate to Fedora?
>
> Isn't this something related to busybox that maybe you should be asking
> about to that community?
>> What value should I put given the output from tune2fs below:
>>
>> tune2fs -l /dev/VolGrp00/LogVol01
>> tune2fs 1.39 (29-May-2006)
>> Filesystem volume name: <none>
>> Last mounted on: <not available>
>> Filesystem UUID: ec03dcbc-2829-4a22-a43f-52dbf1bb5af8
>> 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: 1220935680
>> Block count: 2441864192
>> Reserved block count: 122093209
>> Free blocks: 2403359240
>> Free inodes: 1220931839
>> First block: 0
>> Block size: 4096
>> Fragment size: 4096
>> Reserved GDT blocks: 441
>> Blocks per group: 32768
>> Fragments per group: 32768
>> Inodes per group: 16384
>> Inode blocks per group: 512
>> Filesystem created: Tue Oct 13 18:51:33 2009
>> Last mount time: Wed Oct 14 15:32:47 2009
>> Last write time: Wed Oct 14 15:32:47 2009
>> Mount count: 5
>> Maximum mount count: 29
>> Last checked: Tue Oct 13 18:51:33 2009
>> Check interval: 15552000 (6 months)
>> Next check after: Sun Apr 11 18:51:33 2010
>> Reserved blocks uid: 0 (user root)
>> Reserved blocks gid: 0 (group root)
>> First inode: 11
>> Inode size: 128
>> Journal inode: 8
>> Default directory hash: tea
>> Directory Hash Seed: 72b9b9fe-57dd-433a-815c-de332420a0c5
>> Journal backup: inode blocks
>>
>> Thanks
>> Dan
>>
Fair point. I thought they might be universal terms that guys here
might know what they correlate to in the tune2fs output. I'll keep
quiet on this as it seems to be a sensitive point.
Dan
More information about the users
mailing list