Hi Qu,
Tried it with backup roots and it won't mount. I have a backup of a
week ago and I'll accept the dataloss.
I'll rebuild (this time without BTRFS RAID5/6) and restore.
Thanks for your help!
--
Groet / Cheers,
Patrick Dijkgraaf
On Fri, 2019-10-04 at 09:59 +0200, Patrick Dijkgraaf wrote
Decided to upgrade my system to the latest and give it a shot:
# btrfs check /dev/sde2
Opening filesystem to check...
parent transid verify failed on 4314780106752 wanted 470169 found
470107
checksum verify failed on 4314780106752 found 7077566E wanted 9494EBD8
checksum verify failed on 4314780106
On 2019/10/4 下午3:41, Patrick Dijkgraaf wrote:
> Hi Qu,
>
> I know about RAID5/6 risks, so I won't blame anyone but myself. I'm
> currenlty working on another solution, but I was not quite there yet...
>
> mount -o ro /dev/sdh2 /mnt/data gives me:
>
> [Fri Oct 4 09:36:27 2019] BTRFS info (devi
Hi Qu,
I know about RAID5/6 risks, so I won't blame anyone but myself. I'm
currenlty working on another solution, but I was not quite there yet...
mount -o ro /dev/sdh2 /mnt/data gives me:
[Fri Oct 4 09:36:27 2019] BTRFS info (device sde2): disk space caching
is enabled
[Fri Oct 4 09:36:27 201
On 2019/10/4 下午2:59, Patrick Dijkgraaf wrote:
> Hi guys,
>
> During the night, I started getting the following errors and data was
> no longer accessible:
>
> [Fri Oct 4 08:04:26 2019] btree_readpage_end_io_hook: 2522 callbacks
> suppressed
> [Fri Oct 4 08:04:26 2019] BTRFS error (device sde2
BTRFS restore shows the following output:
#btrfs restore -D /dev/sde2 /mnt/data
This is a dry-run, no files are going to be restored
parent transid verify failed on 4314638041088 wanted 470169 found
470107
parent transid verify failed on 4314638041088 wanted 470169 found
470107
checksum verify fai
Thanks for the help and clarification Qu.
I will wait for the 5.3 and see what it brings.
Best regars,
Konstantin
- Original Message -
From: "Qu Wenruo"
To: "Konstantin V. Gavrilenko" , "linux-btrfs"
Sent: Wednesday, 14 August, 2019 1:24:42 AM
Sub
arhont.com
>
> tel: +44 (0) 870 44 31337
> fax: +44 (0) 208 429 3111
>
> PGP: Key ID - 0xE81824F4
> PGP: Server - keyserver.pgp.com
>
>
> - Original Message -
> From: "Qu Wenruo"
> To: "Konstantin V. Gavrilenko"
> Cc: "linux-b
st try copy the old data to a newly
created btrfs.
Thanks,
Qu
> - is it possible to # btrfs check without copying it back on the
> main disk. maybe loopdevice?
>
>
> thanks,
> Konstantin
>
>
> - Original Message -
> From: "Qu Wenruo"
> To: &q
On 2019/8/13 下午5:48, Konstantin V. Gavrilenko wrote:
> Hi list
>
> I have run the btrfs check, and that reported multiple errors on the FS.
>
> # btrfs check --readonly --force /dev/kubuntu-vg/lv_root
>
Please don't skip the output, especially for btrfs check.
The first tree btrfs check chec
On Fri, Mar 16, 2018 at 7:34 PM, higuita wrote:
> On Tue, 13 Mar 2018 22:24:43 -0600, Chris Murphy
> wrote:
>> c. (optional) take a btrfs image before you do the repair because if
>> something blows up, at least that will help a dev figure out why btrfs
>> check blew up your file system.
>
>
Thanks for the reply!
On Tue, 13 Mar 2018 22:24:43 -0600, Chris Murphy
wrote:
> If you search the list for 'corrupt leaf bad key ordering' the top two
> causes are bad RAM and flaky power supply. These can be hard to narrow
> down.
I will try to get new power supply to test as the curren
If you search the list for 'corrupt leaf bad key ordering' the top two
causes are bad RAM and flaky power supply. These can be hard to narrow
down. But yes pretty good chance it can be fixed with 'btrfs check
--repair' but two things before you do that:
a. Make sure backups are up to date. Hopeful
On 16.10.2017 08:00, Steve Leung wrote:
> On 10/13/2017 03:14 AM, Nikolay Borisov wrote:
>>
>>
>> On 12.10.2017 20:44, Steve Leung wrote:
>>> I've run into a btrfs error trying to do a -j8 build of android on a
>>> btrfs
>>> filesystem exported over NFSv3. That in itself might be unwise, but
>>>
>> TL;DR: ran into some btrfs errors and weird behaviour, but
>> things generally seem to work. Just posting some details in
>> case it helps devs or other users. [ ... ] I've run into a
>> btrfs error trying to do a -j8 build of android on a btrfs
>> filesystem exported over NFSv3. [ ... ]
I have
On 12.10.2017 20:44, Steve Leung wrote:
> Hi list,
>
> TL;DR: ran into some btrfs errors and weird behaviour, but things generally
> seem
> to work. Just posting some details in case it helps devs or other users.
>
> I've run into a btrfs error trying to do a -j8 build of android on a bt
On 10/12/2017 11:44 AM, Steve Leung wrote:
Hi list,
TL;DR: ran into some btrfs errors and weird behaviour, but things generally
seem
to work. Just posting some details in case it helps devs or other users.
I've run into a btrfs error trying to do a -j8 build of android on a btrfs
filesy
On 2015-08-28 11:10, J - wrote:
I have noticed a BTRFS error mentioned in two consecutive identical entries in
my kernel log:
"BTRFS error (device sda2): bad extent! em: [0 0] passed [0 4096]"
sda2 contains a btrfs with skinny extents has been created a few days ago and
contains a few subvolu
On Fri, Aug 28, 2015 at 9:10 AM, J - wrote:
> I have noticed a BTRFS error mentioned in two consecutive identical entries
> in my kernel log:
> "BTRFS error (device sda2): bad extent! em: [0 0] passed [0 4096]"
>
> sda2 contains a btrfs with skinny extents has been created a few days ago and
>
wife has accidently deleted a ton of photos...
-Original Message-
From: Fajar A. Nugraha [mailto:l...@fajar.net]
Sent: Friday, December 02, 2011 7:39 AM
To: Mike Thomas
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs errors
On Fri, Dec 2, 2011 at 7:34 PM, Mike Thomas wrote:
> Hi, I&#x
On Fri, Dec 2, 2011 at 7:34 PM, Mike Thomas wrote:
> Hi, I've been using btrfs for a while now, I've been utilizing snapshotting
> nightly/weekly/monthly. During the weekly I also do a backup of the
> filesystem to an ext4 filesystem. My storage is a linux md raid 5 volume.
> I've recently notic
21 matches
Mail list logo
