Re: Need help with potential ~45TB dataloss

Hi Qu, Thanks for helping me! Please see the reponses in-line. Any suggestions based on this? Thanks! On Sat, 2018-12-01 at 07:57 +0800, Qu Wenruo wrote: > On 2018/11/30 下午9:53, Patrick Dijkgraaf wrote: > > Hi all, > > > > I have been a happy BTRFS user for quite some time. But now I'm > > fa

Re: Need help with potential ~45TB dataloss

I have some additional info. I found the reason the FS got corrupted. It was a single failing drive, which caused the entire cabinet (containing 7 drives) to reset. So the FS suddenly lost 7 drives. I have removed the failed drive, so the RAID is now degraded. I hope the data is still recoverable

Re: Need help with potential ~45TB dataloss

02.12.2018 23:14, Patrick Dijkgraaf пишет: > I have some additional info. > > I found the reason the FS got corrupted. It was a single failing drive, > which caused the entire cabinet (containing 7 drives) to reset. So the > FS suddenly lost 7 drives. > This remains mystery for me. btrfs is mark

Re: Need help with potential ~45TB dataloss

On 2018/12/2 下午5:03, Patrick Dijkgraaf wrote: > Hi Qu, > > Thanks for helping me! > > Please see the reponses in-line. > Any suggestions based on this? > > Thanks! > > > On Sat, 2018-12-01 at 07:57 +0800, Qu Wenruo wrote: >> On 2018/11/30 下午9:53, Patrick Dijkgraaf wrote: >>> Hi all, >>> >>>

Re: Need help with potential ~45TB dataloss

On 2018/12/3 上午8:35, Qu Wenruo wrote: > > > On 2018/12/2 下午5:03, Patrick Dijkgraaf wrote: >> Hi Qu, >> >> Thanks for helping me! >> >> Please see the reponses in-line. >> Any suggestions based on this? >> >> Thanks! >> >> >> On Sat, 2018-12-01 at 07:57 +0800, Qu Wenruo wrote: >>> On 2018/11/30

[PATCH] btrfs-progs: fsck-tests: Move reloc tree images to 020-extent-ref-cases

For reloc tree, despite of its short lifespan, it's still the backref, where reloc tree root backref points back to itself, makes it special. So it's more approriate to put them into 020-extent-ref-cases. Signed-off-by: Qu Wenruo --- tests/fsck-tests/015-tree-reloc-tree/test.sh| 16 ---

Re: Need help with potential ~45TB dataloss

On 2018/12/3 上午4:30, Andrei Borzenkov wrote: > 02.12.2018 23:14, Patrick Dijkgraaf пишет: >> I have some additional info. >> >> I found the reason the FS got corrupted. It was a single failing drive, >> which caused the entire cabinet (containing 7 drives) to reset. So the >> FS suddenly lost 7 d