El 2014-10-29 04:02, Duncan escribió:
Juan Orti posted on Tue, 28 Oct 2014 16:54:19 +0100 as excerpted:
[ 3713.086292] BTRFS: unable to fixup (regular) error at logical
483011874816 on dev /dev/sdb2
[ 3713.092577] BTRFS: checksum error at logical 483011948544 on dev
/dev/sdb2, sector
If right after starting the snapshot creation ioctl we perform a write against a
file followed by a truncate, with both operations increasing the file's size, we
can get a snapshot tree that reflects a state of the source subvolume's tree
where
the file truncation happened but the write operation
Ping..
On Thu, 23 Oct 2014 16:44:54 +0800, Miao Xie wrote:
On Thu, 18 Sep 2014 11:27:17 -0400, Josef Bacik wrote:
Trying to reproduce a log enospc bug I hit a panic in the async reclaim code
during log replay. This is because we use fs_info-fs_root as our root for
shrinking and such.
On Wed, 29 Oct 2014 08:21:12 +, Filipe Manana wrote:
If right after starting the snapshot creation ioctl we perform a write
against a
file followed by a truncate, with both operations increasing the file's size,
we
can get a snapshot tree that reflects a state of the source subvolume's
There will be compatibility issue with this patch running older
kernel, sorry I slipped some combination. As I see this is already in,
I am sending a patch to back out this changes if it helps. Thanks.
On 09/04/14 20:02, Anand Jain wrote:
On 09/04/2014 05:58 PM, David Sterba wrote:
There is a compatibility issue with older kernel with the progs commit id as
below.
05cd2907557ba627cfb86e60b214ea6228613a84
So as of now writing to revert the above commit id.
The brewing sysfs interface would help to fix the impending issue, which is
seed device would fail show in 'btrfs fi
Hi Gui,
We don't need this patch. Actually you should back out this patch to
get this correct.
[PATCH] btrfs-progs: do a separate probe for _transient_ replacing device
OR apply. this
[PATCH] revert btrfs-progs: do a separate probe for _transient_
replacing device
Try it out. Lets
On Wed, 2014-10-29 at 18:56 +0800, Anand Jain wrote:
Hi Gui,
We don't need this patch. Actually you should back out this patch to
get this correct.
[PATCH] btrfs-progs: do a separate probe for _transient_ replacing device
OR apply. this
[PATCH] revert btrfs-progs: do a separate
On Wed, 2014-10-29 at 18:51 +0800, Anand Jain wrote:
There is a compatibility issue with older kernel with the progs commit id as
below.
05cd2907557ba627cfb86e60b214ea6228613a84
Which tree does this commit id belongs to?
I can't find it anywhere?
So as of now writing to revert the above
If right after starting the snapshot creation ioctl we perform a write against a
file followed by a truncate, with both operations increasing the file's size, we
can get a snapshot tree that reflects a state of the source subvolume's tree
where
the file truncation happened but the write operation
Can't find commit in official repos
Get fatal: bad object 915902c5002485fb13d27c4b699a73fb66cc0f09 from git show
Found
commit 2513077f2f830b4bc83d528bfb6979eb461918bd
btrfs-progs: fix device missing of btrfs fi show with seed devices
On Wed, Oct 29, 2014 at 7:57 AM, Filipe Manana fdman...@suse.com
wrote:
If right after starting the snapshot creation ioctl we perform a
write against a
file followed by a truncate, with both operations increasing the
file's size, we
can get a snapshot tree that reflects a state of the
On Mon, Oct 27, 2014 at 04:36:26PM +0800, Qu Wenruo wrote:
Original Message
Subject: Re: [PATCH] btrfs: Enhance btrfs chunk allocation algorithm
to reduce ENOSPC caused by unbalanced data/metadata allocation.
From: Liu Bo bo.li@oracle.com
To: Qu Wenruo
On Oct 29, 2014, at 2:08 AM, Juan Orti juan.o...@miceliux.com wrote:
El 2014-10-29 04:02, Duncan escribió:
Juan Orti posted on Tue, 28 Oct 2014 16:54:19 +0100 as excerpted:
[ 3713.086292] BTRFS: unable to fixup (regular) error at logical
483011874816 on dev /dev/sdb2
[ 3713.092577] BTRFS:
This is new in my eyes, or ? :
Oct 29 17:53:04 n22kvmclone kernel: INFO: trying to register non-static key.
Oct 29 17:53:04 n22kvmclone kernel: the code is fine but needs lockdep
annotation.
Oct 29 17:53:04 n22kvmclone kernel: turning off the locking correctness
validator.
Oct 29 17:53:04
$ sudo mount -o degraded,ro /dev/sdd1 /asdf
mount: wrong fs type, bad option, bad superblock on /dev/sdd1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
$ dmesg | tail
[524718.760792] BTRFS info
Dear Sir
Did your website get hit by Google Penguin update on October 17th 2014? What
basically is Google Penguin Update? It is actually a code name for Google
algorithm which aims at decreasing your websites search engine rankings that
violate Googles guidelines by using black hat SEO
I'm in the middle of debugging the exact same thing. 3.17.0 -
rtorrent dies with SIGBUS.
I've done some debugging, the sequence is something like this:
open a new file
fallocate() to the final size
mmap() all (or a portion) of the file
write to the region
run SHA1 on that mmap'd region to
Filed bug here with more details and complete dmesg attached:
https://bugzilla.kernel.org/show_bug.cgi?id=87131
kernel-3.18.0-0.rc2.git1.1.fc22.x86_64
SUMMARY:
After umount returning to prompt, and physical disconnected 2x devices (btrfs
raid1 on raw devices), I get a backtrace with some scary
On 10/28/2014 01:32 PM, Zack Coffey wrote:
Made a RAID1 with another drive of just the metadata. Was in
that state for less than 12 hours-ish, removed the second drive and
now cannot get to any data on the original drive. Data remained single
while only metadata was RAID1.
I don't know all the
The following code reliably throws a SIGBUS in the memset, and cat
testfile /dev/null returns an IO error.
I've sometimes gotten as high as iteration 900 before a SIGBUS, so
don't assume a single clear is OK.
linux 3.17.0, SATA - MD(raid5) - bcache (ssd) - btrfs
Working on eliminating more
On 10/29/2014 03:26 PM, Robert White wrote:
On 10/28/2014 01:32 PM, Zack Coffey wrote:
Made a RAID1 with another drive of just the metadata. Was in
that state for less than 12 hours-ish, removed the second drive and
now cannot get to any data on the original drive. Data remained single
while
Original Message
Subject: Re: [PATCH] btrfs: Enhance btrfs chunk allocation algorithm to
reduce ENOSPC caused by unbalanced data/metadata allocation.
From: Liu Bo bo.li@oracle.com
To: Qu Wenruo quwen...@cn.fujitsu.com
Date: 2014年10月29日 22:29
On Mon, Oct 27, 2014 at
Extract the procedure of searching for a target device for fi show
from the @map_seed_devices() function to make it more clear.
Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com
---
cmds-filesystem.c | 37 -
1 file changed, 28 insertions(+), 9 deletions(-)
Stalling problems may happen when exec balance fi show cmds concurrently.
With the following commit:
commit 915902c500
btrfs-progs: fix device missing of btrfs fi show with seed devices
The fi show cmd will bother the mounted fs when only umounted fs should
be handled after
Before the patch, chunk will be considered bad if the corresponding
block group is missing, even the only uncertain data is the 'used'
member of the block group.
This patch will try to recalculate the 'used' value of the block group
and rebuild it.
So even only chunk item and dev extent item is
It's specifically BTRFS related, I was able to reproduce it on a bare
drive (no lvm, no md, no bcache). It's not bad RAM, I was able to
reproduce it on multiple machines running either 3.17 or late RCs.
I've tested 3.18-rc2 for about 2 hours now, can't get any failures, so
that's good. If
just notice your case is different from others seen/working on.
in your the layout has issue. its not about the raid. sorry.
try: mount -o recovery,ro
On 10/30/2014 03:32 AM, Zack Coffey wrote:
$ sudo mount -o degraded,ro /dev/sdd1 /asdf
mount: wrong fs type, bad option, bad superblock
Original Message
Subject: Re: [PATCH] btrfs: Enhance btrfs chunk allocation algorithm to
reduce ENOSPC caused by unbalanced data/metadata allocation.
From: Qu Wenruo quwen...@cn.fujitsu.com
To: bo.li@oracle.com
Date: 2014年10月30日 08:58
Original Message
yes that's the one.
btrfs-progs: fix device missing of btrfs fi show with seed devices
Thanks
On 10/29/2014 08:15 PM, Rene Thomas wrote:
Can't find commit in official repos
Get fatal: bad object 915902c5002485fb13d27c4b699a73fb66cc0f09 from git show
Found
There is a compatibility issue with older kernel with the progs commit id as
below.
d0588bfa479409b2a0f6243f894338a01a56221a
btrfs-progs: do a separate probe for _transient_ replacing device
So as of now writing to revert the above commit id.
The brewing sysfs interface would help to fix the
my ws commit ids have changed may be when I was to trying nail down an
issue some time back. Thanks. V2. is out.
On 10/29/2014 07:41 PM, Gui Hecheng wrote:
On Wed, 2014-10-29 at 18:51 +0800, Anand Jain wrote:
There is a compatibility issue with older kernel with the progs commit id as
32 matches
Mail list logo
