Hello, I have a simple fileserver that performs a nightly backup to an extra disk mounted at /backup using rsync with --link-dest.
The backup disk is normally mounted read-only except when rsync is running. A few days ago i figured it would be interesting to enable softdeps on the backup disk to make the rsync go faster, I then noticed that the softdep option had been removed after the next backup job had completed. I recreated it on my laptop running a recent snapshot like this: /etc/fstab: 76510836242844b3.i /usr/src ffs rw,nodev,nosuid,softdep,ro 1 2 After boot mount reports this: /dev/sd0i on /usr/src type ffs (local, nodev, nosuid, read-only, softdep) Then I update it to read/write which works as I expect: # mount -uw /usr/src /dev/sd0i on /usr/src type ffs (local, nodev, nosuid, softdep) However, once I update it to read-only again the softdep flag is removed: # mount -ur /usr/src /dev/sd0i on /usr/src type ffs (local, nodev, nosuid, read-only) I realize mount(8) states that the "softdep" option is ignored when using -u and the filesystem is mounted read/write, but is this applicable when the filesystem is already mounted with softdep prior to the update? I can of course work around this by just doing a proper umount/mount of the filesystem at the end of the backup job but I was wondering if this was the expected behaviour or not. Finally, while browsing the lists for clues i ran across this post by Stuart: http://marc.info/?l=openbsd-misc&m=132511441117536&w=2 Since rsync with --link-dest is pretty much creating a hardlink tree, maby I shouldn't be using softdeps at all for this? Regards, Patrik Lundin
