[PATCH v4 2/7] btrfs: cleanup barrier_all_devices() unify dev error count

2017-04-05 Thread Anand Jain
Now when counting number of error devices we don't need to count them separately once during send and wait, as because device error counted during send is more of static check. Also kindly note that as of now there is no code which would set dev->bdev = NULL unless device is missing. However I sti

[PATCH 3/4 V2] btrfs: cleanup barrier_all_devices() unify dev error count

2017-03-31 Thread Anand Jain
Now when counting number of error devices we don't need to count them separately once during send and wait, as because device error counted during send is more of static check. Also kindly note that as of now there is no code which would set dev->bdev = NULL unless device is missing. However I sti

Re: [PATCH 3/4] btrfs: cleanup barrier_all_devices() unify dev error count

2017-03-14 Thread Qu Wenruo
At 03/13/2017 03:42 PM, Anand Jain wrote: Now when counting number of error devices we don't need to count them separately once during send and wait, as because device error counted during send is more of static check. Also kindly note that as of now there is no code which would set dev->bdev

[PATCH 3/4] btrfs: cleanup barrier_all_devices() unify dev error count

2017-03-13 Thread Anand Jain
Now when counting number of error devices we don't need to count them separately once during send and wait, as because device error counted during send is more of static check. Also kindly note that as of now there is no code which would set dev->bdev = NULL unless device is missing. However I sti

Re: [PATCH] btrfs-progs: Don't increase error count if the inode can be repaired.

2014-12-21 Thread Satoru Takeuchi
e item > can be repaired in try_repair_inode(), check_inode_recs() should not > increase the error count if the inode can be repair. > > With this patch, repair function for leaf-corruption will not return > error if all corruption inode can be recovered. > > Signed-off

[PATCH] btrfs-progs: Don't increase error count if the inode can be repaired.

2014-12-21 Thread Qu Wenruo
() should not increase the error count if the inode can be repair. With this patch, repair function for leaf-corruption will not return error if all corruption inode can be recovered. Signed-off-by: Qu Wenruo --- cmds-check.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

Re: error count

2013-08-10 Thread Chris Samuel
On Sat, 10 Aug 2013 07:19:27 PM Russell Coker wrote: > But what does generation_errs mean? I'm seeing some on one system. > Should I be concerned? If I write a Nagios check which ones should be > warnings and which ones errors? All I know is that ioctl.h says: BTRFS_DEV_STAT_GENERATION_ERRS

Re: error count

2013-08-10 Thread Russell Coker
On Sat, 10 Aug 2013, Chris Samuel wrote: > On Sun, 4 Aug 2013 03:37:22 PM Bart Noordervliet wrote: > > a sufficiently up-to-date kernel and btrfs tool will provide the > > 'btrfs device stats' command, which should give you the info you want. > > This is what it looks like: > > chris@quad:~/Down

Re: error count

2013-08-09 Thread Chris Samuel
On Sun, 4 Aug 2013 03:37:22 PM Bart Noordervliet wrote: > a sufficiently up-to-date kernel and btrfs tool will provide the > 'btrfs device stats' command, which should give you the info you want. This is what it looks like: chris@quad:~/Downloads/Linux/FileSystems/BtrFS/btrfs-progs$ sudo ./btrfs

Re: error count

2013-08-04 Thread Bart Noordervliet
ative log messages. > > But it doesn't seem possible to get a count of the number of errors. I think > that at the minimum I should be able to get a count of the number of errors > from a device since it was attached to the system. I think that the ideal > would be to have an e

error count

2013-08-04 Thread Russell Coker
would be to have an error count stored on the device and available to the sysadmin. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to