On Tue, Oct 17, 2006 at 10:06:36AM +0200, Oliver Fromme wrote:
> Rick C. Petty wrote:
> > I doubt you'd get the code to work under 6.x or 5.x even. I'm not sure if
> > any GEOM-related stuff ever made it into fsck, but certainly the background
> > checking code and softupdates changes were intr
Rick C. Petty wrote:
> VANHULLEBUS Yvan wrote:
> > Could it be interesting (and quite safe !) to recompile 4.X's fsck
> > under FreeBSD6 and do the test again on FreeBSD 6 ?
>
> I doubt you'd get the code to work under 6.x or 5.x even. I'm not sure if
> any GEOM-related stuff ever made it i
On Monday 16 October 2006 04:15, VANHULLEBUS Yvan wrote:
> On Mon, Oct 16, 2006 at 09:49:04AM +0200, VANHULLEBUS Yvan wrote:
> > On Fri, Oct 13, 2006 at 01:57:58PM -0500, Rick C. Petty wrote:
> [fscking a RO partition]
> > > Grr, I meant 4.x not 5.x, and I thought the problem started about the
tim
On Mon, Oct 16, 2006 at 09:49:04AM +0200, VANHULLEBUS Yvan wrote:
>
> Right: I just tried on a FreeBSD 4.11, and I can fsck a partition
> which has just been remounted RO.
>
> Could it be interesting (and quite safe !) to recompile 4.X's fsck
> under FreeBSD6 and do the test again on FreeBSD 6 ?
On Mon, Oct 16, 2006 at 09:49:04AM +0200, VANHULLEBUS Yvan wrote:
> On Fri, Oct 13, 2006 at 01:57:58PM -0500, Rick C. Petty wrote:
[fscking a RO partition]
> > Grr, I meant 4.x not 5.x, and I thought the problem started about the time
> > bg fsck was introduced...
>
> Right: I just tried on a Free
On Fri, Oct 13, 2006 at 01:57:58PM -0500, Rick C. Petty wrote:
> On Fri, Oct 13, 2006 at 02:16:51PM -0400, John Baldwin wrote:
[fscking a RO partition]
> > I think it's broken in 5.x as well. It's fallout from GEOM IIRC, and it is
> > annoying.
>
> Grr, I meant 4.x not 5.x, and I thought the prob
On Fri, Oct 13, 2006 at 02:16:51PM -0400, John Baldwin wrote:
> On Friday 13 October 2006 13:42, Rick C. Petty wrote:
> >
> > I'm pretty sure that's what he tried (hence "remounted readonly"). I've
> > noticed this behavior as well and it is quite frustrating. If you boot
> > single-user, / will
On Friday 13 October 2006 13:42, Rick C. Petty wrote:
> On Fri, Oct 13, 2006 at 10:04:07AM +0200, Joerg Sonnenberger wrote:
> > On Fri, Oct 13, 2006 at 09:41:37AM +0200, VANHULLEBUS Yvan wrote:
> > >
> > > Later, if root filesystem is remounted readonly, then fsck is called,
> > > it will says "NO
On Fri, Oct 13, 2006 at 10:04:07AM +0200, Joerg Sonnenberger wrote:
> On Fri, Oct 13, 2006 at 09:41:37AM +0200, VANHULLEBUS Yvan wrote:
> >
> > Later, if root filesystem is remounted readonly, then fsck is called,
> > it will says "NO WRITE ACCESS".
>
> mount -ur /
I'm pretty sure that's what he
On Fri, Oct 13, 2006 at 10:04:07AM +0200, Joerg Sonnenberger wrote:
> On Fri, Oct 13, 2006 at 09:41:37AM +0200, VANHULLEBUS Yvan wrote:
> >
> > Later, if root filesystem is remounted readonly, then fsck is called,
> > it will says "NO WRITE ACCESS".
>
> mount -ur /
>
> or if your fstab is not ma
On Fri, Oct 13, 2006 at 09:41:37AM +0200, VANHULLEBUS Yvan wrote:
>
> Later, if root filesystem is remounted readonly, then fsck is called,
> it will says "NO WRITE ACCESS".
mount -ur /
or if your fstab is not matching the system configuration
mount -ur /dev/$ROOT /
Joerg
_
Hi all.
I didn't really know where to post this question, so I try
"hackers"
When rc starts, root filesystem is already mounted readonly, and fsck
runs ok, then root is remounted read/write.
Later, if root filesystem is remounted readonly, then fsck is called,
it will says "NO WRITE ACCESS
12 matches
Mail list logo
