[arch-general] mount shows hardcoded stripe=4 mount option for ext* /boot fs
I first stumbled upon this two years ago and opened a thread in the forum to ask about it [1]. I never got an answer but lived happy and forgetful about it, until some days ago another user PMed me to know if I had ever found out why mount consistently showed `stripe=4` as a mount option for the `/boot` partition, whether or not we leave it in /etc/fstab of use `defaults`. This piqued my interest again, so I'm submitting it here in hope somebody can enlighten us. Please see the original post for all the details. I can confirm that to this day, `$ mount | grep stripe` still returns /dev/mapper/boot-arch on / type ext4 (rw,stripe=4,data=ordered) but `# journalctl -b | grep stripe` returns kernel: EXT4-fs (dm-$): mounted filesystem with ordered data mode. Opts: (null) Cheers [1] https://bbs.archlinux.org/viewtopic.php?id=176092
Sun, 13 Mar 2016 15:27:39 +0100
Bastien Traverse
[...]
Hm, interesting indeed. Can you show the output of 'lvdisplay -v /dev/mapper/boot-arch' and 'tune2fs -l /dev/mapper/boot-arch' ? --byte
Sun, 13 Mar 2016 15:41:44 +0100 Jens Adam <jra at byte.cx>:
Can you show the output of 'lvdisplay -v /dev/mapper/boot-arch' and 'tune2fs -l /dev/mapper/boot-arch' ?
Sure thing: # lvdisplay -v /dev/mapper/boot-arch --- Logical volume --- LV Path /dev/boot/arch LV Name arch VG Name boot LV UUID vo0hGd-MyzZ-HEcp-haYs-Hl8e-WPfR-nwReTB LV Write Access read/write LV Creation host, time archiso, 2013-12-04 15:56:42 +0100 LV Status available # open 1 LV Size 252,00 MiB Current LE 63 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:0 # tune2fs -l /dev/mapper/boot-arch tune2fs 1.42.13 (17-May-2015) Filesystem volume name: archboot Last mounted on: /boot Filesystem UUID: 2100b574-b048-41b9-8fbc-bd7338e3c9c8 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 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: 64512 Block count: 258048 Reserved block count: 12902 Free blocks: 214621 Free inodes: 64163 First block: 1 Block size: 1024 Fragment size: 1024 Reserved GDT blocks: 256 Blocks per group: 8192 Fragments per group: 8192 Inodes per group: 2016 Inode blocks per group: 252 RAID stride: 4 RAID stripe width: 4 Flex block group size: 16 Filesystem created: Wed Dec 4 16:12:41 2013 Last mount time: Sat Mar 12 13:26:22 2016 Last write time: Sat Mar 12 13:26:22 2016 Mount count: 405 Maximum mount count: -1 Last checked: Wed Dec 4 16:12:41 2013 Check interval: 0 (<none>) Lifetime writes: 22 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 5d29516b-d465-4ac2-a0ec-028fbf43f017 Journal backup: inode blocks Thanks for your interest! -- Bastien
I may be way off on this but I did a grep on /etc for stripe and found the reference was in /etc/lvm/lvm.conf and since you said you had logical volumes I thought perhaps this might help. Google'ng ext4 options returns some useful info as well. Something about allocation of blocks. Regards On 03/13/2016 09:27 AM, Bastien Traverse wrote:
/dev/mapper/boot-arch on / type ext4 (rw,stripe=4,data=ordered)
participants (3)
-
Bastien Traverse
-
Jens Adam
-
Marshall Neill