Hi Anand
On 15/09/2014 18:42, Anand Jain wrote:
The patch fixes the issue, although it took a little tweaking to get it
to apply cleanly.
I'm working with Sam. This is what I applied, and it works:
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 340a92d..2c87b72 100644
---
An user reported this, it is because that lseek's SEEK_SET/SEEK_CUR/SEEK_END
allow a negative value for @offset, but btrfs's SEEK_DATA/SEEK_HOLE don't
prepare for that and convert the negative @offset into unsigned type,
so we get (end start) warning.
[ 1269.835374] [ cut here
On 09/15/2014 12:09 PM, Anand Jain wrote:
Sam,
Thanks for reporting. Can you apply the following diff
on top of 3.17rc5 and check if it helps.
---
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index e9676a4..1224b61 100644
--- a/fs/btrfs/volumes.c
+++
On Sat, Sep 13, 2014 at 04:41:00PM +0200, Toralf Förster wrote:
On 09/01/2014 03:41 PM, Liu Bo wrote:
I believe that this warning of btrfs_evict_inode also comes from a result of
lseek, and Chris said that he's prepared a fix for that, so it's queued in
the
next version.
thanks,
So, I just recently had to hard reset a system running root on BTRFS,
and when it tried to come back up, it chocked on the root filesystem.
Based on the kernel messages, the primary issue is log corruption, and
in theory btrfs-zero-log should fix it. The actual issue however, is
that the primary
Hi all,
I have a server running debian 7.5 and meet issues for mounting a btrfs
filesystem. This fs had worked for almost one year now but crashed last
sunday. I'm unable to mount the fs and each btrfs-* commands ends with
something like :
Ignoring transid failure
btrfsck: ctree.c:1550:
Playing around with this filesystem I hot-removed a device from the
array and put in a replacement.
Label: 'Root' uuid: d71404d4-468e-47d5-8f06-3b65fa7776aa
Total devices 2 FS bytes used 7.43GiB
devid1 size 9.31GiB used 8.90GiB path /dev/sdc6
devid3 size 9.31GiB
On Sep 16, 2014, at 9:54 AM, Tovo Rabemanantsoa
tovo.rabemanant...@bordeaux.inra.fr wrote:
Hi all,
I have a server running debian 7.5 and meet issues for mounting a btrfs
filesystem. This fs had worked for almost one year now but crashed last
sunday. I'm unable to mount the fs and each
http://marc.info/?l=linux-btrfsm=136733749808576w=2
https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#How_do_I_report_bugs_and_issues.3F
Should both kernel and btrfs-progs bugs be filed at bugzilla.kernel.org? And if
not, where should btrfs-progs bugs be filed?
Chris Murphy--
To unsubscribe
Sorry, that was really just a sample of output rather then a
run-through of my steps. Also, I captured an image of the partition
so I could re-install my OS.
I did try btrfs-zero-log first, but not btrfs rescue super-recover (as
I was afraid it might break my superblock).
I will try the latest
The smart stats on the disk are fine. The /dev/sdc messages are from me
playing around and pulling out the drive. btrfs fi show, shows the
drive as missing, yet it's still trying to write to it.
Basically my goal is to remove this drive and stick it in another box
and I can't get btrfs to
Hi-
I'm doing a project that involves, among other things, measuring the
block write overhead that reference counting snapshots imposes in
btrfs, and I wanted to run my methodology by the mailing list, to see
if there were any holes in it. I'm counting backrefs here as
reference counts, since
On 09/16/2014 07:17 PM, Chris Murphy wrote:
Debian 7.5 is based on kernel 3.2 which is very old in Btrfs terms. What
kernel version are you using, and version of btrfs-progs?
Chris Murphy
You're right,
In the beginning, I used the btrfs-progs provided by my debian (kernel
3.2.0-4 and btrfs
From: li...@colorremedies.com
Date: Tue, 16 Sep 2014 11:26:16 -0600
On Sep 16, 2014, at 10:51 AM, Mark Murawski markm-li...@intellasoft.net
wrote:
Playing around with this filesystem I hot-removed a device from the
array and put in a replacement.
Label: 'Root' uuid:
When doing log replay we may have to update inodes, which traditionally goes
through our delayed inode stuff. This will try to move space over from the
trans handle, but we don't reserve space in our trans handle on replay since we
don't know how much we will need, so instead we try to flush.
On Sep 16, 2014, at 8:40 AM, Austin S Hemmelgarn ahferro...@gmail.com wrote:
Based on the kernel messages, the primary issue is log corruption, and
in theory btrfs-zero-log should fix it.
Can you provide a complete dmesg somewhere for this initial failure, just for
reference? I'm curious
On Sep 16, 2014, at 1:36 PM, Tony Murray murrayt...@gmail.com wrote:
Sorry, that was really just a sample of output rather then a
run-through of my steps. Also, I captured an image of the partition
so I could re-install my OS.
I did try btrfs-zero-log first, but not btrfs rescue
On Sep 16, 2014, at 1:54 PM, Mark Murawski markm-li...@intellasoft.net wrote:
The smart stats on the disk are fine. The /dev/sdc messages are from me
playing around and pulling out the drive. btrfs fi show, shows the drive as
missing, yet it's still trying to write to it.
That's known.
On Sep 16, 2014, at 2:11 PM, Tovo Rabemanantsoa
tovo.rabemanant...@bordeaux.inra.fr wrote:
On 09/16/2014 07:17 PM, Chris Murphy wrote:
Debian 7.5 is based on kernel 3.2 which is very old in Btrfs terms. What
kernel version are you using, and version of btrfs-progs?
Chris Murphy
You're
https://bugzilla.redhat.com/show_bug.cgi?id=1142421
kernel-3.17.0-0.rc5.git0.1.fc22.x86_64
btrfs-progs-3.16-1.fc21.x86_64
Steps to Reproduce:
1. mkfs.btrfs /dev/sdc
2. btrfs check --subvol-extents /dev/sdc
Results:
Segmentation fault (core dumped)
[ 632.749774] btrfs[692]: segfault at 0 ip
On 9/16/14 4:33 PM, Chris Murphy wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1142421
kernel-3.17.0-0.rc5.git0.1.fc22.x86_64
btrfs-progs-3.16-1.fc21.x86_64
Steps to Reproduce:
1. mkfs.btrfs /dev/sdc
2. btrfs check --subvol-extents /dev/sdc
Results:
Segmentation fault (core
Stefan,
Can you pls send me the output for
cat /etc/fstab | egrep btrfs
cat /proc/self/mounts | egrep btrfs
mount | egrep btrfs
Thanks, Anand
On 17/09/2014 05:08, Stefan G. Weichinger wrote:
Am 15.09.2014 um 19:42 schrieb Anand Jain:
Sam,
In the above context, Can you
Johannes, Xavier,
Can you pls send the output for ..
cat /etc/fstab | egrep btrfs
cat /proc/self/mounts | egrep btrfs
mount | egrep btrfs
Thanks, Anand
On 16/09/2014 06:17, Johannes Hirte wrote:
On Tue, 16 Sep 2014 01:39:49 +0800
Anand Jain anand.j...@oracle.com wrote:
On
The journal file is opened with O_DIRECT | O_DSYNC. I can reproduce
it somewhat readily with a ceph-osd process on some of our hardware.
I'm trying to create a non-ceph reproducer, but I figured that this
might be enough to go on in the mean time. What additional
information would be useful?
I've just released version 0.4.1 of buttersink. As of this version, I
consider it beta and out of the experimental phase.
Buttersink will synchronize a set of read-only snapshots in a btrfs
filesystem to an Amazon S3 bucket, and vice-versa. It intelligently
picks parent snapshots to diff from
Hi all,
What work would be required to mark btrfs_fs_type with FS_USERNS_MOUNT
so that btrfs images can be mounted by unprivileged users within a user
namespace (along with something like [1])? I'd like to be able to create
disk images without having to start a VM (and --rootdir isn't flexible
On Tue, Sep 16, 2014 at 11:05:00PM -0400, Shea Levy wrote:
Hi all,
What work would be required to mark btrfs_fs_type with FS_USERNS_MOUNT
so that btrfs images can be mounted by unprivileged users within a user
namespace (along with something like [1])? I'd like to be able to create
disk
Root is mounted. This is the same picture after several reboots.
I've actually did some switching things around, drive swaps and some
expansions but it's still oddly displayed.
Label: 'Root' uuid: d71404d4-468e-47d5-8f06-3b65fa7776aa
Total devices 2 FS bytes used 5.81GiB
28 matches
Mail list logo
