Package: e2fsprogs Version: 1.43.4-2 Severity: wishlist File: /sbin/tune2fs
We run # tune2fs -U time /dev/sdb1 tune2fs 1.43.4 (31-Jan-2017) Please run e2fsck -f on the filesystem. and $? = 1 Problems: The message should clarify: Does this mean the task (changing the UUID) is done, and now we should run e2fsck ? Does this mean the task is not done, and now we should run e2fsck, and run the task again? (OK, tune2fs -l /dev/sdb1 shows it probably means the latter, as the UUID is the same as before.) # e2fsck -f /dev/sdb1 e2fsck 1.43.4 (31-Jan-2017) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sdb1: 12/108968 files (8.3% non-contiguous), 24310/434177 blocks # tune2fs -U time /dev/sdb1 tune2fs 1.43.4 (31-Jan-2017) Setting UUID on a checksummed filesystem could take some time. Proceed anyway (or wait 5 seconds) ? (y,N) <proceeding> Here a giant surprise occurs just as we are reading the word "or". One would have thought "or" was related to the word "proceed", as in "do something different than". But then out pops the word "<proceeding>". ... which is quite in contrast to the y,N that probably means N if one hits RET. So the default for RET is N, and the default for slow readers is Y. I recall we discussed this about something else but I am offline as I write this. P.S., the man page should say that -U can only be run after recent e2fsck. (A second tune2fs -l /dev/sdb1 shows the task is now indeed done!)
