[DragonFlyBSD - Bug #1330] Hammer, usb disk, SYNCHRONIZE CACHE failure

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Mon Jun 2 04:56:16 PDT 2014


Issue #1330 has been updated by tuxillo.

Category changed from Other to Unverifiable
Target version changed from 3.8.0 to Unverifiable

Moving to unverifiable. We need that specific hardware to test it. Feel free to update the ticket if any relevant testing is performed on current releases.

----------------------------------------
Bug #1330: Hammer, usb disk, SYNCHRONIZE CACHE failure
http://bugs.dragonflybsd.org/issues/1330#change-12000

* Author: josepht
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: Unverifiable
* Target version: Unverifiable
----------------------------------------
This is for 2.2-RELEASE.  I have a 2.5" drive in an external USB
enclosure with one big Hammer filesystem on it.  The disk is ~75GB.
When the daily cronjob to cleanup hammer runs it fails with these
errors:

Thanks,
Joe

Apr  6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 
Apr  6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
Apr  6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
Apr  6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:20,0
Apr  6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): Invalid command operation code
Apr  6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): 
SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:20,0
Apr  6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): Invalid command operatio n code
Apr  6 03:02:10 jupiter kernel: Unretryable error
Apr  6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): error 22
Apr  6 03:02:10 jupiter kernel: (da0:umass-sim0:0:0:0): Unretryable Error
Apr  6 03:02:10 jupiter kernel: HAMMER(DATA): Critical error inode=-1 while flushing meta-data
Apr  6 03:02:10 jupiter kernel: HAMMER(DATA): Forcing read-only mode
Apr  6 03:02:10 jupiter kernel: HAMMER(DATA): Critical write error during flush, refusing to sync UNDO FIFO



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



More information about the Bugs mailing list