On Tue, 15 Dec 2009, Richard W.M. Jones wrote:
> On Mon, Dec 14, 2009 at 10:35:49PM +0200, Szabolcs Szakacsits wrote:
> >
> > The problem is qemu "silently falling back to opening the block device
> > read-only" and keep telling it's RW instead of returning EROFS.
> >
> > NTFS-3G can handle errors when lower layers report an error, not when they
> > say "everything is fine, please keep doing it".
>
> > > [ 2.698844] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > > [ 2.700865] ata1.00: BMDMA stat 0x5
> > > [ 2.701944] ata1.00: cmd ca/00:01:30:da:5f/00:00:00:00:00/e0 tag 0 dma
> > > 512 out
> > > [ 2.701945] res 41/04:01:30:da:5f/00:00:00:00:00/e0 Emask 0x1
> > > (device error)
> > > [ 2.706525] ata1.00: status: { DRDY ERR }
> > > [ 2.707757] ata1.00: error: { ABRT }
> > > [ 2.714183] ata1.00: configured for MWDMA2
> > > [ 2.715482] ata1: EH complete
>
> This doesn't look to me like "everything is fine". Are you saying
> that NTFS-3g / FUSE doesn't see the abort exceptions being sent from
> the IDE layer?
Yes. It's not enough to log errors. It should be also told to the upper
layers.
Szaka
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
