gjournal & fsck

Pawel Jakub Dawidek pjd at FreeBSD.org
Thu Aug 28 19:26:29 UTC 2008


On Thu, Aug 28, 2008 at 11:03:49AM -0400, Brian McCann wrote:
> On Thu, Aug 28, 2008 at 10:51 AM, Ivan Voras <ivoras at freebsd.org> wrote:
> >
> > Does gjournal complain about your drive, for example that it doesn't
> > support BIOFLUSH?
> 
> Actually yes...I meant to post them in my last message, but hit send
> too early...here's my output from boot (from dmesg.boot)
> 
> GEOM_JOURNAL: Journal 478661671: da1 contains data.
> GEOM_JOURNAL: Journal 478661671: da1 contains journal.
> GEOM_JOURNAL: Journal da1 clean.
> (da1:mly0:4:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
> (da1:mly0:4:1:0): CAM Status: SCSI Status Error
> (da1:mly0:4:1:0): SCSI Status: Check Condition
> (da1:mly0:4:1:0): ILLEGAL REQUEST asc:24,0
> (da1:mly0:4:1:0): Invalid field in CDB
> (da1:mly0:4:1:0): Unretryable error
> GEOM_JOURNAL: BIO_FLUSH not supported by da1.
> GEOM_JOURNAL: Journal 3065355517: da2 contains data.
> GEOM_JOURNAL: Journal 3065355517: da2 contains journal.
> GEOM_JOURNAL: Journal da2 clean.
> (da2:mly1:4:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
> (da2:mly1:4:0:0): CAM Status: SCSI Status Error
> (da2:mly1:4:0:0): SCSI Status: Check Condition
> (da2:mly1:4:0:0): ILLEGAL REQUEST asc:24,0
> (da2:mly1:4:0:0): Invalid field in CDB
> (da2:mly1:4:0:0): Unretryable error
> GEOM_JOURNAL: BIO_FLUSH not supported by da2.
> 
> >
> > Also, did fsck actually do something when it was started (did it find
> > anything corrupted)?
> >
> No...it didn't find anything wrong / anything to fix.  (and one of the
> file systems was being written to at the time...so at least journaling
> appears to be working)  Something else I noticed...Manolis' article
> says it should say "journal xxxx consistent"...whereas mine says
> "Journal xxxx clean".  I don't know what the differences mean, or what
> the BIO_FLUSH means...but I'm hoping you can tell me. :)

Don't worry about those if you have memory-backed RAID card. BIO_FLUSH
is there to tell the disk to flush its write caches, but if it is
memory-backed, there is low risk on losing unwritted data.

This is not the cause of your problem.

BTW. "journal ... clean" means that there was clean shutdown and there
was no need to replay journal, while "journal ... consistent" means that
there was unclean shutdown and journal replay was successful.

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20080828/3cf047f9/attachment.pgp


More information about the freebsd-questions mailing list