I run:
od -x /tmp/corrupt-dev2.txt > a
od -x /tmp/corrupt-dev1.txt > b
cmp a b;
diff a b;
looks like both files are identical, means that both metadata files
got corrupted?
thanks
On Thu, Apr 21, 2016 at 8:53 AM, lenovomi wrote:
> Hello Liu,
>
> please find both files stored here:
>
> https:
Hello Liu,
please find both files stored here:
https://drive.google.com/folderview?id=0B6RZ_9vVuTEcMDV6eGNmRlZ0ZjQ&usp=sharing
Thanks
On Thu, Apr 21, 2016 at 7:27 AM, Liu Bo wrote:
> On Wed, Apr 20, 2016 at 10:09:07PM +0200, lenovomi wrote:
>> Hi Chris,
>>
>> please find below attached t
On 2016/04/20 14:17, Matthias Bodenbinder wrote:
Am 18.04.2016 um 09:22 schrieb Qu Wenruo:
BTW, it would be better to post the dmesg for better debug.
So here we. I did the same test again. Here is a full log of what i did. It
seems to be mean like a bug in btrfs.
Sequenz of events:
1. mount
Liu Bo wrote on 2016/04/20 23:02 -0700:
On Thu, Apr 21, 2016 at 01:43:56PM +0800, Qu Wenruo wrote:
Matthias Bodenbinder wrote on 2016/04/21 07:22 +0200:
Am 20.04.2016 um 09:25 schrieb Qu Wenruo:
Unfortunately, this is the designed behavior.
The fs is rw just because it doesn't hit any c
On Thu, Apr 21, 2016 at 01:43:56PM +0800, Qu Wenruo wrote:
>
>
> Matthias Bodenbinder wrote on 2016/04/21 07:22 +0200:
> >Am 20.04.2016 um 09:25 schrieb Qu Wenruo:
> >
> >>
> >>Unfortunately, this is the designed behavior.
> >>
> >>The fs is rw just because it doesn't hit any critical problem.
>
On Tue, Apr 19, 2016 at 02:51:33PM -0700, Eric Wheeler wrote:
> On Wed, 13 Apr 2016, Eric Wheeler wrote:
>
> > Hello all,
> >
> > We just got this backtrace in 4.4.6 on an ARM AM335x (beaglebone
> > compatible). The trace looks similar to this one:
> > http://permalink.gmane.org/gmane.comp.fi
Matthias Bodenbinder wrote on 2016/04/21 07:22 +0200:
Am 20.04.2016 um 09:25 schrieb Qu Wenruo:
Unfortunately, this is the designed behavior.
The fs is rw just because it doesn't hit any critical problem.
If you try to touch a file and then sync the fs, btrfs will become RO
immediately.
On Wed, Apr 20, 2016 at 10:09:07PM +0200, lenovomi wrote:
> Hi Chris,
>
> please find below attached the complete log while executing all the
> brtrfs commands, all of them failed.
>
> ;-(
>
>
> https://bpaste.net/show/4d8877a49b80
> https://bpaste.net/show/7e2e5aa30741
> https://bpaste.net/sho
Am 20.04.2016 um 09:25 schrieb Qu Wenruo:
>
> Unfortunately, this is the designed behavior.
>
> The fs is rw just because it doesn't hit any critical problem.
>
> If you try to touch a file and then sync the fs, btrfs will become RO
> immediately.
>
> Btrfs fails to read space cache, no
Am 20.04.2016 um 15:32 schrieb Anand Jain:
>> 1. mount the raid1 (2 disc with different size)
>
>> 2. unplug the biggest drive (hotplug)
>
> Btrfs won't know that you have plugged-out a disk.
> Though it experiences IO failures, it won't close the bdev.
Well, as far as I can tell mdadm can h
On Mon, Apr 18, 2016 at 01:18:31AM +0200, Dmitry Katsubo wrote:
> On 2016-04-14 22:30, Dmitry Katsubo wrote:
> > Dear btrfs community,
> >
> > I have the following setup:
> >
> > # btrfs fi show /home
> > Label: none uuid: 865f8cf9-27be-41a0-85a4-6cb4d1658ce3
> > Total devices 3 FS bytes use
Don't think I've reported this one before. It's on the same box I've been
seeing the btrfs_destroy_inode WARN_ON's on though.
Dave
BTRFS: assertion failed: num_extents, file: fs/btrfs/extent-tree.c, line: 5584
[ cut here ]
kernel BUG at fs/btrfs/ctree.h:4320!
inval
On 2016-04-19 09:58, Duncan wrote:
> Dmitry Katsubo posted on Tue, 19 Apr 2016 07:45:40 +0200 as excerpted:
>
>> Actually btrfs restore has recovered many files, however I was not able
>> to run in fully unattended mode as it complains about "looping a lot".
>> Does it mean that files are corrupte
On Wed, Apr 20, 2016 at 2:09 PM, lenovomi wrote:
> Hi Chris,
>
> please find below attached the complete log while executing all the
> brtrfs commands, all of them failed.
>
> https://bpaste.net/show/482e91b25fc5
>warning, device 1 is missing
>warning, device 2 is missing
Restore probably can't
Hi Chris,
please find below attached the complete log while executing all the
brtrfs commands, all of them failed.
;-(
https://bpaste.net/show/4d8877a49b80
https://bpaste.net/show/7e2e5aa30741
https://bpaste.net/show/482e91b25fc5
https://bpaste.net/show/5093cc3daa5a
https://bpaste.net/show/a249
Pretty much all commands print out the usage message when no device is
specified:
[root@host ~]# btrfs scrub start
btrfs scrub start: too few arguments
usage: btrfs scrub start [-BdqrRf] [-c ioprio_class -n ioprio_classdata]
|
...
However, balance doesn't
[root@host ~]# btrfs balance start
ERROR
On Wed, Apr 20, 2016 at 10:02:27AM +0800, Qu Wenruo wrote:
> Hi David,
>
> Any new comment about the ondisk format and ioctl interface?
Hi Qu,
I'm at LSF this week but will dig through again on the way home.
Thanks!
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs
On Tue, 19 Apr 2016 15:19:46 -0700, Mark Fasheh wrote:
> On Fri, Apr 15, 2016 at 05:08:22PM +0800, Qu Wenruo wrote:
>> Current btrfs qgroup design implies a requirement that after calling
>> btrfs_qgroup_account_extents() there must be a commit root switch.
>>
>> Normally this is OK, as btrfs_qgr
1. mount the raid1 (2 disc with different size)
2. unplug the biggest drive (hotplug)
Btrfs won't know that you have plugged-out a disk.
Though it experiences IO failures, it won't close the bdev.
3. try to copy something to the degraded raid1
This will work as long as you do _no
Sorry. Its typo I used original disk /dev/sdb where filesystem is
created and seeing these errors.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Matthias Bodenbinder wrote on 2016/04/20 07:17 +0200:
Am 18.04.2016 um 09:22 schrieb Qu Wenruo:
BTW, it would be better to post the dmesg for better debug.
So here we. I did the same test again. Here is a full log of what i did. It
seems to be mean like a bug in btrfs.
Sequenz of events:
1.
21 matches
Mail list logo