Messages in this thread | | | Date | Wed, 26 May 2004 14:49:44 +0200 | From | Jens Axboe <> | Subject | Re: 2.6.6-mm5 |
| |
On Wed, May 26 2004, Anders Gustafsson wrote: > On Sat, May 22, 2004 at 01:36:36AM -0700, Andrew Morton wrote: > > > > - Implementation of request barriers for IDE and SCSI. The idea here is > > that a filesystem can tag an IO request as a barrier and the disk will not > > reorder writes across the barrier. It provides additional integrity > > guarantees for the journalling filesystems. The feature is enabled for > > reiserfs and ext3. > > I get: this error message when using barriers on a scsi disk: > > lost page write due to I/O error on sdb1 > JBD: barrier-based sync failed on sdb1 - bisabling barriers > > and I don't want them barriers bisabled :) > > ext3 filesystem. reiser also disables barriers. > > I have a "Adaptec AIC-7902 U320 (rev 3)" SCSI controller and the disk is a > SEAGATE ST373307LW.
But they need to be bisabled, since -o barrier doesn't work on SCSI yet. Only non-data tagged flushes are supported, those from blkdev_issue_flush().
-- Jens Axboe
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |