Anyway I was experimenting more and discovered something
against docs. These time I created newfs on pendrive so if fs get corrupted
it will not break nothing. It will be dd-zeroed and
formatted anyway.
Manual of mount says:
The options async and softdep are mutually exclusive.
But I have discov
You mean using async?
I don't usually use async.
I did used async a few times today experimenting
with mount /home with no intention to use async later.
Fortunately crash have not happened during these
experiments.
Actually noasync is redundant for this script, because
I don't use async in fstab.
> So I should do something like that:
> sudo /sbin/mount -u -o noasync,sync,rw,nodev,nosuid,noatime /home
No, you should not.
Because if you do experience a system crash, damage can occur to the
filesystem which fsck cannot recover from. With such a configurations,
on-disk operations can happen
So I should do something like that:
sudo /sbin/mount -u -o noasync,sync,rw,nodev,nosuid,noatime /home
Sorry for this bug report.
On 2016/09/03 16:23, Lampshade wrote:
> Sometimes I have crash (unrelated to this bug)
> during halt -p, so I decided to remount /home
> as sync just before I execute halt -p.
> During testing I have discovered unexpected
> behaviour of mount(8).
>
> Mount is printing that I have FFS filesystem
>
Sometimes I have crash (unrelated to this bug)
during halt -p, so I decided to remount /home
as sync just before I execute halt -p.
During testing I have discovered unexpected
behaviour of mount(8).
Mount is printing that I have FFS filesystem
mounted as asynchronous and synchronous
at the same ti
