Re: [PATCH 1/2] Btrfs: be more precise on errors when getting an inode from disk

2016-07-22 Thread J. Bruce Fields
On Fri, Jul 22, 2016 at 12:40:26PM +1000, NeilBrown wrote: > On Fri, Jul 22 2016, J. Bruce Fields wrote: > > > On Fri, Jul 22, 2016 at 11:08:17AM +1000, NeilBrown wrote: > >> On Fri, Jun 10 2016, fdman...@kernel.org wrote: > >> > >> > From: Filipe Manana > >> > > >> > When we

Re: [PATCH 1/2] Btrfs: be more precise on errors when getting an inode from disk

2016-07-21 Thread NeilBrown
On Fri, Jul 22 2016, J. Bruce Fields wrote: > On Fri, Jul 22, 2016 at 11:08:17AM +1000, NeilBrown wrote: >> On Fri, Jun 10 2016, fdman...@kernel.org wrote: >> >> > From: Filipe Manana >> > >> > When we attempt to read an inode from disk, we end up always returning an >> >

Re: [PATCH 1/2] Btrfs: be more precise on errors when getting an inode from disk

2016-07-21 Thread J. Bruce Fields
On Fri, Jul 22, 2016 at 11:08:17AM +1000, NeilBrown wrote: > On Fri, Jun 10 2016, fdman...@kernel.org wrote: > > > From: Filipe Manana > > > > When we attempt to read an inode from disk, we end up always returning an > > -ESTALE error to the caller regardless of the actual

Re: [PATCH 1/2] Btrfs: be more precise on errors when getting an inode from disk

2016-07-21 Thread NeilBrown
On Fri, Jun 10 2016, fdman...@kernel.org wrote: > From: Filipe Manana > > When we attempt to read an inode from disk, we end up always returning an > -ESTALE error to the caller regardless of the actual failure reason, which > can be an out of memory problem (when allocating a

[PATCH 1/2] Btrfs: be more precise on errors when getting an inode from disk

2016-06-09 Thread fdmanana
From: Filipe Manana When we attempt to read an inode from disk, we end up always returning an -ESTALE error to the caller regardless of the actual failure reason, which can be an out of memory problem (when allocating a path), some error found when reading from the