You are not logged in.
Hello,
I have two identical hard drives. Both have a gparted created GPT table and a CLI created ext4 filesystem with no options other than -L (label).
Both are mounted with identical fstab options:
LABEL=Archiv_1 /mnt/Archiv_1 ext4 defaults
LABEL=Archiv_2 /mnt/Archiv_2 ext4 defaultsArchiv_1 was created like two weeks before Archiv_2 (which was created right now). I don't know about exact kernel versions, but:
root@horus /home/florian # mount
[...]
/dev/sde1 on /mnt/Archiv_1 type ext4 (rw,relatime)
/dev/sdd1 on /mnt/Archiv_2 type ext4 (rw,relatime,data=ordered)
/dev/sdb1 on /home type ext4 (rw,relatime,data=ordered)I am curious why Archiv_1 and 2 have different mount options applied? If default options have changed in the last two weeks, why has /home the same options like Archiv_2 though it's much older?
What mount options would you recommend for ext4 disks that are primarily used for bulk data storage?
Thanks!
Last edited by Osiris (2013-05-21 17:04:22)
Offline
Compare the output of 'tune2fs -l /dev/sde1 | grep "mount options"' with the output of 'tune2fs -l /dev/sdd1 | grep "mount options"' and see if they are different.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Nope, they are identical:
root@horus /mnt/Archiv_2 # tune2fs -l /dev/sde1 | grep "mount options"
Default mount options: user_xattr acl
root@horus /mnt/Archiv_2 # tune2fs -l /dev/sdd1 | grep "mount options"
Default mount options: user_xattr aclCould it be related to disk usage?
Offline
No idea then, maybe some mount helper changed the mount options for those partitions. You will have to wait for someone else to chime in with more ideas.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Seems to be systemd related.
root@horus ~ # systemctl show mnt-Archiv_1.mount > A1
root@horus ~ # systemctl show mnt-Archiv_2.mount > A2
root@horus ~ # diff -y A1 A2
[...]
Where=/mnt/Archiv_1 | Where=/mnt/Archiv_2
What=/dev/sde1 | What=/dev/sdd1
Options=rw,relatime,rw | Options=rw,relatime,rw,data=ordered
[...]
The unit files for the mounts in /run/systemd/generator show no difference there.
Last edited by Osiris (2013-05-21 20:48:07)
Offline
Seems to be systemd related.
<snip>
The unit files for the mounts in /run/systemd/generator show no difference there.
If the unit files are the same, how is this related to systemd?
Strongly suspect tune2fs isn't giving you the full story and this is simply the kernel following the FS.
Last edited by falconindy (2013-05-21 21:05:30)
Offline
You seem to be right.
Archiv_1 has:
Filesystem features: ext_attr resize_inode dir_index filetype sparse_super large_file
Archiv_2:
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
I thought I used mkfs.ext4 on both in the same way. Filesystem magic number is identical.
Why is Archiv_1 without journal?
Offline
The partitions are exactly identical, the drives are the same manufactor, same series, ...
Offline