> On Nov 25, 2015, at 8:44 PM, Qu Wenruo <[email protected]> wrote: > > > > Vincent Olivier wrote on 2015/11/25 11:51 -0500: >> I should probably point out that there is 64GB of RAM on this machine and >> it’s a dual Xeon processor (LGA2011-3) system. Also, there is only Btrfs >> served via Samba and the kernel panic was caused Btrfs (as per what I >> remember from the log on the screen just before I rebooted) and happened in >> the middle of the night when zero (0) client was connected. >> >> You will find below the full “btrfs check” log for each device in the order >> it is listed by “btrfs fi show”. > > There is really no need to do such thing, as btrfs is able to manage multiple > device, calling btrfsck on any of them is enough as long as it's not hugely > damaged. > >> >> Ca I get a strong confirmation that I should run with the “—repair” option >> on each device? Thanks. > > YES. > > Inode nbytes fix is *VERY* safe as long as it's the only error. > > Although it's not that convincing since the inode nbytes fix code is written > by myself and authors always tend to believe their codes are good.... > But at least, some other users with more complicated problem(with inode > nbytes error) fixed it. > > The last decision is still on you anyway.
I will do it on the first device from the “fi show” output and report. Thanks, Vincent -- 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
