Is there any inode flag (or anything equivalent) indicating that
writing that particular inode to the device failed because of an IO
error?
I couldn't find one or determine what am I supposed to do when that happens
TIA
Martin
-
To unsubscribe from this list: send the line unsubscribe
it. What happens to these pages later on?
Does the memory manager attempt to write them again? Is the error
somehow signalled to anyone? Do filesystems try to relocate the data
from bad blocks of the device?
TIA
Martin Jambor
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel
Can I try to bring your attention once more to the following issue:
On 4/18/05, Martin Jambor [EMAIL PROTECTED] wrote:
There is one thing about cache pages and buffers that puzzles me and
that I have not found in any documenatation and that is not quite
obvious from the source.
What
metadata mean, in true kernel naming confusion
spirit, device pages/blocks?).
Can anyone tell me what the relationship exactly is and what one has
to be aware of when manipulating either of these?
Thank you very much in advance,
Martin Jambor
-
To unsubscribe from this list: send the line
? Would some other
part of kernel break if there was a bunch of buffers assigned to the
same spot on the disk?
On the other hand, if I understand buffer flags correctly, I need to
be able to emulate mapping of buffers to set them dirty, or em I
wrong?
Thanks for any insight or thoughts,
Martin Jambor
is accessed. Don't know how to do that or if you
would need to be platform specific, though.
HTH
Martin Jambor
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
