since my first question got answers, here are answers to questions 2 and 3:
2: there's a problem report here:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108968
this still exists in CURRENT
3: i believe it takes so long to do fsck on a device in background mode
because a snapshot has to be t
On Wed, 23 Sep 2009 23:20:22 +0200 (CEST), Alexander Best
wrote:
> thx. i thought since / gets mounted read-only and fsck is able to check it
> with write access this would apply to read-only mountpoints in general.
Because fsck resides in /sbin, it is required - in SUM - that /
is mounted and a
Polytropon schrieb am 2009-09-23:
> On Wed, 23 Sep 2009 17:02:24 +0200 (CEST), Alexander Best
> wrote:
> > however if i do `mount -r -o noatime /dev/label/usr /usr` and run
> > `fsck
> > /dev/label/usr` fsck isn't able to gain write access.
> The fsck program should - as far as I know - only be u
On Wed, 23 Sep 2009 17:02:24 +0200 (CEST), Alexander Best
wrote:
> however if i do `mount -r -o noatime /dev/label/usr /usr` and run `fsck
> /dev/label/usr` fsck isn't able to gain write access.
The fsck program should - as far as I know - only be used on
unmounted (!) file systems. In order to
hi there,
i've stumbled over some issues running 9-CURRENT i386 (r197427) and would like
to ask if these are in fact problems/bugs or the way things are meant to work.
isssue 1:
when booting into single user mode / (dev/label/rootfs) gets mounted
read-only. when doing `fsck /dev/label/rootfs` pro
