Could one of those mount flags cause any harm with a RAIDframe array ?
/dev/dk0 on /export type ffs (asynchronous, log, noatime, NFS exported,
local)
well well, it seems like removing the `async' flag solved the issue, I've just
ran multiple tests that caused instant fail yesterday which
On Fri, Jan 03, 2014 at 07:38:21PM +0100, Emile `iMil' Heitor wrote:
Could one of those mount flags cause any harm with a RAIDframe array ?
/dev/dk0 on /export type ffs (asynchronous, log, noatime, NFS exported, local)
I am surprised you can combine async and log but I would strongly
asynchronous + log should be impossible.
I've just discovered that the hard way :)
Did you find out wether the system is really hanging or just very slow?
In particular, is there any disk activity and does the system respond
on the network?
Like I said earlier on this thread, the system
In Message alpine.neb.2.00.1401032034540.15...@korriban.imil.net,
Emile `iMil' Heitor i...@home.imil.netwrote:
=
= asynchronous + log should be impossible.
=
=I've just discovered that the hard way :)
FWIW, it is documented in mount(8):
log (FFS only) Mount the file
FWIW, it is documented in mount(8):
log (FFS only) Mount the file system with wapbl(4) meta-
data journaling, also known simply as logging. It
provides rapid metadata updates and eliminates the
need