Hi,
Setting the `compression` property on a subvolume on Linux 4.0-rc2 with
btrfs-progs 3.18.2 causes the error `BTRFS error (device sda5): error
inheriting props for ino [inode] (root 419): -28` to be logged to
`/var/log/syslog` (where `[inode]` is a number). I assume that setting
compression on
Hi,
The manpage of `btrfs property` would be a good place to explain the
precedence of properties over mount options, e.g. what happens when the
mount option `compress` is set to `zlib` and the property for same
subvolume is set to `` (indicating no compression as you know)? What
happens when
Hi,
According to
https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#How_do_I_report_bugs_and_issues.3F
bugs ought to be reported on bugzilla.kernel.org and on the mailing
list. Is and to be interpreted as a logical AND or rather XOR. If the
former is the case, is it sufficient to set the mailing
Hi,
Now I could rebuild the csum tree with `--repair --init-csum-tree` with
3.18.2 on Linux 3.19, see the attached output for the things which were
fixed and probably caused the problem.
Thanks for your suggestions!
Best regards,
Kalle
Am 16.02.2015 um 12:19 schrieb Karl-Philipp Richter:
Hi
v3.18.2
On Mon, Feb 16, 2015 at 3:42 AM, Qu Wenruo quwen...@cn.fujitsu.com wrote:
Original Message
Subject: Re: btrfs check --init-csum-tree removes csums again
From: Chris Murphy li...@colorremedies.com
To: Karl-Philipp Richter rich...@richtercloud.de
Date: 2015年02月16日 13:59
Hi,
After running `btrfs check --init-csum-tree` 3.18.2 and 3.19-rc2 on a
btrfs all checksums are gone (thousands of line in the form of `no csum
found for inode X start Y` in `/var/log/kern.log`). I know that this
behavior (to delete all csums) was a stub in a dev version and remember
that it was
Hi,
After running `sudo btrfs rescue chunk-recover -y -v /dev/loop0` with 4
unrecoverable chunks (of 619) I'm having trouble with `btrfsck` which logs
parent transid verify failed on 4210688 wanted 61241 found 7983179
Ignoring transid failure
apparently for ever (let it run for 1 hour
Hi,
Just to give you a really late feedback on this: I got it fixed with
btrfs-progs 3.17.3n on Linux 3.17.6, i.e. `btrfs rescue chunk-recover`
just did the job. Thanks for your advice.
-Kalle
Am 09/16/2014 um 03:46 AM schrieb Gui Hecheng:
On Mon, 2014-09-15 at 16:59 +0200, Karl-Philipp Richter
Hi together,
after a btrfs was missing some csums and therefore remounted read-only,
I unmounted it and experienced
$ sudo btrfsck --init-csum-tree /dev/sde1
Creating a new CRC tree
Checking filesystem on /dev/sde1
UUID: bd6298ea-0748-45fe-87c8-eace6793ca89
Reinit crc root
Hi together,
I'm currently encountering another issue with `btrfs rescue
chunk-recover`. After some seconds of maximal I/O activity, the program
is idle for some seconds and then prints
The chunks in memory can not match the metadata of the fs. Repair
failed.
Fail to recover the
Hi together,
In the current HEAD (3f11e516db629f7a662bfd6376231817b4e34cc9) of
https://github.com/kdave/btrfs-progs.git (I assume this list is the
right address because I got some hints to the project from here) the
btrfs restore subcommand asks often (up to 100 time during restauration
of 400 GB)
, Karl-Philipp Richter
krich...@posteo.de wrote:
Hi together,
In the current HEAD (3f11e516db629f7a662bfd6376231817b4e34cc9) of
https://github.com/kdave/btrfs-progs.git (I assume this list is the
right address because I got some hints to the project from here) the
btrfs restore subcommand asks
Hi,
I could `btrfsck --repair` the sparse file with Linux 3.15.6-utopic from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ and btrfsck 3.12-1 (from
btrfs-tools package in Ubuntu 14.04).
Thanks for your hints, Wang!
All the best,
Karl
Am 18.07.2014 14:13, schrieb Wang Shilong:
Hi,
There
Am 25.06.2014 03:20, schrieb Gui Hecheng:
On Tue, 2014-06-24 at 15:43 +0200, Karl-Philipp Richter wrote:
Hi together,
I wondered whether
$ sudo btrfs rescue chunk-recover -y /dev/loop2p1
btrfs: chunk-recover.c:124: process_extent_buffer: Assertion
`!(exist-nmirrors = 2)' failed
Hi together,
I'm experiencing the following issues when I invoke `btrfsck` on a
sparse file image with a GPT and one (the only) btrfs partition attached
to a loop device
$ sudo btrfsck --repair --init-csum-tree --init-extent-tree -b
/dev/loop0p1
Incorrect local backref count on
Hi together,
I wondered whether
$ sudo btrfs rescue chunk-recover -y /dev/loop2p1
btrfs: chunk-recover.c:124: process_extent_buffer: Assertion
`!(exist-nmirrors = 2)' failed.
$ echo $?
134
is an error in btrfs or an error message of (the correctly working)
btrfs. Any ideas what
Hi together,
I've created a btr(fs) filesystem on a partition on a qcow2 image with
GUID partition table created with qemu (1.7.0) tool:
qemu-img create -f qcow2 image.qcow2 2T
I'm connecting this image to a NBD with qemu-nbd and mounting the NBD.
I'm experiencing errors which I don't with
Hi together,
I'm new to the list and hope to be at the right place for the following
issue:
The wiki page
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories#btrfs_kernel_module_git_repository
talks about integrating an existing local kernel clone (instance) by
adding it as a git
18 matches
Mail list logo