Updating to ext4
To do this, you can use common applications like gparted to label partitions or you can use e2label to label ext2, ext3, and ext4 partitions. Labels should be unambiguous, meaning that each label should be original to prevent any possible conflicts.
Keep in mind that not all file system have labeling support (e.g. A device or partition must not be mounted before attempting to label them.
[[email protected] labfiles]$ stat nursery File: `nursery' Size: 837 Blocks: 8 IO Block: 4096 regular file Device: fd00h/64768d Inode: 139539 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 500/ juan) Gid: ( 500/ juan) Access: 2013-10-22 .703888346 -0400 Modify: 2013-10-21 .801165793 -0400 [email protected] labfiles]$ vi nursery [[email protected] labfiles]$ stat nursery File: `nursery' Size: 837 Blocks: 8 IO Block: 4096 regular file Device: fd00h/64768d Inode: 139539 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 500/ juan) Gid: ( 500/ juan) Access: 2013-10-22 .703888346 -0400 Modify: 2013-10-21 .801165793 -0400 Change: 2013-10-21 .801165793 -0400 [[email protected] labfiles]$ mount /dev/mapper/vg_jnlnxsvr02-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0") /dev/sda1 on /boot type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) [[email protected] labfiles]$ noatime Do not update inode access times on this filesystem (e.g., for faster access on the news spool to speed up news servers).
relatime Update inode access times relative to modify or change time.
From the example of my /etc/fstab above, the UUID is no longer unique and it will mount the first partition it finds with that UUID.
Note: I've put a bounty on this and have unassigned @enkore (who was assigned on this for rather long).
Note that this is obviously non-standard behaviour and is not officially supported.
I would say with a fair bit of confidence that in this and most scenarios, the Linux partition UUID has more of a local machine scope.Access time is only updated if the previous access time was earlier than the current modify or change time.(Similar to noatime, but doesn't break mutt or other applications that need to know if a file has been read since the last time it was modified.) Since Linux 2.6.30, the kernel defaults to the behavior provided by this option (unless noatime was specified), and the strictatime option is required to obtain traditional semantics.While doing "corruption testing" (results below) with various file systems (NTFS-3g, ext4, XFS)  I noticed that given just the right sequence of operations  one can manage to put some data in a freshly created repository on XFS and then lose the repo config rendering the repo unusable until an advanced power-user re-creates the config file.I don't think this is a critical/big problem in normal usage patterns since the first create after an init will almost certainly take longer than the dirty-writeout timeout of the kernel (one to a couple minutes). That live/visible metadata refers to non-existing MFT entries suggests (in my mind) that some basic precondition of the journaling must've been broken.
Search for updating to ext4:
) (or file systems table) file is a system configuration file on Debian systems.