Re: I/O errors block the entire filesystem

2013-05-15 Thread Josef Bacik
On Sat, May 11, 2013 at 01:16:38AM -0600, Alexandre Oliva wrote: On Apr 4, 2013, Alexandre Oliva ol...@gnu.org wrote: I've been trying to figure out the btrfs I/O stack to try to understand why, sometimes (but not always), after a failure to read a (data non-replicated) block from the

Re: I/O errors block the entire filesystem

2013-05-15 Thread Alexandre Oliva
On May 14, 2013, Liu Bo bo.li@oracle.com wrote: In one of the failures that caused machine load spikes, I tried to collect info on active processes with perf top and SysRq-T, but nothing there seemed to explain the spike. Thoughts on how to figure out what's causing this? Although I've

Re: I/O errors block the entire filesystem

2013-05-15 Thread Alexandre Oliva
On May 15, 2013, Josef Bacik jba...@fusionio.com wrote: So this should only happen in the case that you are on a dm device it looks like, is that how you are running? That was my first thought, but no, I'm using partitions out of the SATA disks directly. I even checked for stray dm out of

Re: I/O errors block the entire filesystem

2013-05-14 Thread Liu Bo
On Thu, Apr 04, 2013 at 01:10:27PM -0300, Alexandre Oliva wrote: I've been trying to figure out the btrfs I/O stack to try to understand why, sometimes (but not always), after a failure to read a (data non-replicated) block from the disk, the file being accessed becomes permanently locked, and

Re: I/O errors block the entire filesystem

2013-05-11 Thread Alexandre Oliva
On Apr 4, 2013, Alexandre Oliva ol...@gnu.org wrote: I've been trying to figure out the btrfs I/O stack to try to understand why, sometimes (but not always), after a failure to read a (data non-replicated) block from the disk, the file being accessed becomes permanently locked, and the

I/O errors block the entire filesystem

2013-04-04 Thread Alexandre Oliva
I've been trying to figure out the btrfs I/O stack to try to understand why, sometimes (but not always), after a failure to read a (data non-replicated) block from the disk, the file being accessed becomes permanently locked, and the filesystem, unmountable. Sometimes (but not always) it's