Huh. If I do an strace of a dd of the drive once, it works for a
while, ^C and start again and the strace hangs on a read() syscall!
So... seems like a hardware problem that coincided with the drive
filling up. Or something!
This will be my first btrfs raid1 replacement, so I'm hoping its
It is still hanging afterall. Currently, it hangs on mount:
[154422.778624] mount D0 27894 27742 0x0084
[154422.778625] Call Trace:
[154422.779018] __schedule+0x28d/0x880
[154422.779494] schedule+0x36/0x80
[154422.779886] io_schedule+0x16/0x40
[154422.780288]
If there's no hung task listed in dmesg you could try to do sysrq+t to
find out what everything's up to, although then you have to learn how
to parse the result.
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to
I have a mount point that became ... hung for lack of a better word.
I was doing a LARGE sort of a file in it, using temporary files in
that directory, and the
system hung and probably the watchdog kicked in, reset the system.
Upon reboot, the filesystem hung if you touched it. Processes were
