On Fri, Mar 29, 2013 at 07:06:33AM -0600, Swâmi Petaramesh wrote: > Hi Josef, > > Le 29/03/2013 13:58, Josef Bacik a écrit : > > So this is probably because of the extent tree corruption you had, it's just > > cleaning things up and you should be fine once it finishes. Thanks, > > Er... It's on a different machine ! > > Current (at the time I write) status is : > > # btrfs scrub status / > scrub status for 346b81b2-0735-4c4d-a137-1995bc78ad70 > scrub resumed at Fri Mar 29 11:52:43 2013 and finished after > 7470 seconds > total bytes scrubbed: 231.96GB with 149691 errors > error details: csum=149691 > corrected errors: 149691, uncorrectable errors: 0, unverified > errors: 0 > > I have to say that scrub completely froze the machine at least 4 times > (disk had ceased activity and any command that would imply a disk access > would hang forever), but at least after a (quite brutal) reboot it could > be resumed... > > The only thing about this FS is that it had been imaged, then restored, > using partclone.btrfs (which itself is supposed to use the BTRFS libraries). > > I have a screenshot of "last thing I saw when it hanged", I can upload > it somewhere, should it be relevant... >
Actually instead of netconsole we have an awesome service provided by Carey, you can just do nc cwillu.com 10101 < /dev/kmsg after you've run sysrq+w and then reply with the URL it spits out. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
