gjournal & fsck

[Manolis Kiagias]

Brian McCann wrote:
> On Thu, Aug 28, 2008 at 11:03 AM, Brian McCann <bjmccann at gmail.com> 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. :)
>>
>> Thanks again!
>> --Brian
>>
>>     
>
> I should probably also mention that this is on a Mylex 2000 RAID
> controller...with a RAID-5 array and using write-caching.
>
> Thanks
> --Brian
>   

I don't have any "exotic"  hardware myself - the article was written 
with standard SATA disks as examples.
As I understand, the "consistent" message comes up when the journal is 
actually used to return the filesystem to a consistent state (what would 
happen after a power failure, when the filesystem is "dirty") and the 
"clean" message means there was no inconsistency between the filesystem 
and journal (a normat shutdown of the filesystem).  If it comes up as 
"clean", I wonder why fsck kicks in at all...