gjournal + WARNING: R/W mount of / denied. Filesystem not clean - run fsck.

illoai at gmail.com illoai at gmail.com
Tue Jun 12 04:00:50 UTC 2007


On 11/06/07, Niki Denev <ndenev at totalterror.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Niki Denev wrote:
> > Wilkinson, Alex wrote:
> >>     0n Wed, Jun 06, 2007 at 06:45:26PM +0300, Niki Denev wrote:
> >
> >>     > I have the following problem when using gjournal for the root filesystem on my laptop (Sony VAIO PCG-U3)
> >>     > If there is a unclean shutdown (hard poweroff/ kernel panic) on the next boot the machine starts to load normally,
> >>     > i have messages as :
> >>     >
> >>     >        GEOM_JOURNAL: Journal ad0s1a consistent.
> >>     >        Trying to mount root from ufs:/dev/ad0s1a.journal
> >>     >        WARNING: / was not properly dismounted
> >>     >
> >>     > Then the system continues with executing fsck  in preen mode (fsck -p),
> >>     > which reports :
> >>     >        /dev/ad0s1a.journal: FILESYSTEM CLEAN; SKIPPING CHECKS
> >>     > and fsck returns with zero, but after this when a read/write mount is tried the
> >>     > system barfs this :
> >>     >
> >>     >        WARNING: R/W mount of / denied. Filesystem not clean - run fsck.
> >>     >        mount:  : Operation not permitted
> >
> >> Make sure your "Pass" column is correct in fstab(5).
> >
> > What do you mean by correct? Right now it's the default for root
> > filesystems "1". Is there a special setting needed for gjournaled
> > filesystems?
> >
> >
>
> Well, i still can't find a way to make my system skip fsck on unclean
> shutdown/reboot.
> The strange thing is that "fsck -p" reports that the filesystem is
> clean, but the kernel refuses to mount it r/w with the message "WARNING:
> R/W mount of / denied. Filesystem is not clean - run fsck"
>
> I guess i'm doing something wrong.. just can't see what it is.. any
> ideas are appreciated.

Have you tried fsck without the -p flag?

I don't know if fixit mode from the CDROM
would do any good on gjournal, though I
don't see why the module couldn't be loaded
if it existed there.  As a last resort you might
be able to blow the journal away without
mangling your / (I will play with gjournal some
to-night, perhaps).

-- 
--


More information about the freebsd-current mailing list