Ted Ts'o, on 08/06/2010 01:17 AM wrote:
On Thu, Aug 05, 2010 at 11:29:59PM +0400, Vladislav Bolkhovitin wrote:
Have you had a chance to check out whether this patch solves the
problem you were complaining with respect to yanking out the last
iSCSI or FC link to a hard drive, and then umounting the disk
afterwards?
Looks like it works. I was able to reach that branch (see AAA in the
attached log) and it was handled well.
OK, great!
I've also got other (see the attached log file):
1. A bunch of detected hung tasks with call traces.
Is this unique to ext4? It looks like a problem where we're either
(a) not getting an I/O error from the block device in time before we
get the hung task timeout (which might be the right thing, if the link
eventually comes back --- what I've seen is there's a no clear
consensus how long the last FC or iSCSI link should be done before we
give up on an I/O operation), or (b) for some reason we're not
noticing the I/O error and waiting forever. I believe (a) is more
likely here, but it's possible it's (b). Do you eventually get file
system I/O errors that abort the journal transaction? You should...
Yes, as you can see in the previously attached log.
2. "JBD: recovery failed" I reported before.
I've searched my mail archives, and I'm not sure what you're talking
about here. Maybe this was in an e-mail that you sent that perhaps
got lost?
It's next to the message on which you originally replied. It was about
ext3, but this time I saw it with ext4.
Thanks,
Vlad
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
