From: Namjae Jeon
This patch is a follow up on below patch:
[PATCH] exportfs: add FILEID_INVALID to indicate invalid fid_type
commit: 216b6cbdcbd86b1db0754d58886b466ae31f5a63
Signed-off-by: Namjae Jeon
Signed-off-by: Vivek Trivedi
Acked-by: Steven Whitehouse
---
fs/btrfs/export.c |4
The condition can be relaxed to accept also 0 which will delete
unoccupied chunks and does not need space for the actual data
relocation. Until there is an automatic empty chunk reclaim, we
can use this as a last resort option under enospc.
CC: Ilya Dryomov
Signed-off-by: David Sterba
---
Also
On Mon, Feb 11, 2013 at 04:28:43PM +0400, Alexey Polyakov wrote:
> Hi!
> I created filesystem with two devices, 200gb partition each, raid1
> both for data and metadata, and 16k leaf and node size. After using it
> for day or two I got checksum error on one file. scrub reported about
> 70 more simi
On Sun, Feb 10, 2013 at 10:21:31PM +0530, nafisa mandliwala wrote:
> Hello,
> We're a team of 4 final year computer science students and are
> working on generating a diff between file system snapshots using the
> send receive code.
Looks like a duplicated effort. Did you see Mark's initia
On Sat, Feb 09, 2013 at 11:21:16AM -0800, Blair Zajac wrote:
> Running an Ubuntu Raring VM which was built a week ago that is now running
> 3.8-rc6, I was booting it last night when it hung. After a few forced
> reboots, it came back up and I found the attached in kern.log.
>
> Are these reports
I have just completed installing an archlinux machine with 2 btrfs
partitions, one works fine (the rootfs), the other one I cannot mount.
Even after recreating the filesystem I still cannot mount it. I
receive te following output in my dmesg:
[ 6526.037089] device fsid 74cc8eb8-f60a-4797-9ab3-0c8a
On Mon, Feb 11, 2013 at 4:49 PM, David Sterba wrote:
> On Mon, Feb 11, 2013 at 04:28:43PM +0400, Alexey Polyakov wrote:
>
> Did you use a kernel version between 3.8-rc1 and 3.8-rc5 ?
I used 3.8-rc6 and 3.8-rc7 when working with fs in question, but also
I mounted it under kernel that Ubuntu ships,
On Mon, Feb 11, 2013 at 02:09:56PM +0100, Sjon Hortensius wrote:
> I have just completed installing an archlinux machine with 2 btrfs
> partitions, one works fine (the rootfs), the other one I cannot mount.
> Even after recreating the filesystem I still cannot mount it. I
> receive te following out
Acked-by: Sage Weil
On Mon, 11 Feb 2013, Namjae Jeon wrote:
> From: Namjae Jeon
>
> This patch is a follow up on below patch:
>
> [PATCH] exportfs: add FILEID_INVALID to indicate invalid fid_type
> commit: 216b6cbdcbd86b1db0754d58886b466ae31f5a63
>
> Signed-off-by: Namjae Jeon
> Signed-off
On Mon, Feb 11, 2013 at 2:27 PM, David Sterba wrote:
> On Mon, Feb 11, 2013 at 02:09:56PM +0100, Sjon Hortensius wrote:
>> I have just completed installing an archlinux machine with 2 btrfs
>> partitions, one works fine (the rootfs), the other one I cannot mount.
>> Even after recreating the files
On Thu, Jan 31, 2013 at 03:03:06PM +0200, Alex Lyakas wrote:
> # umount may get delayed because of pending-for-deletion subvolumes:
> btrfs_commit_super() locks the cleaner_mutex, so it will wait for the
> cleaner to complete.
> On the other hand, cleaner will not give up until it completes
> proce
On Sun, Feb 10, 2013 at 03:35:05PM -0700, Gordon Manning wrote:
>Hi,
>Is the BTRFS raid code susceptible to RAID-5 write holes? �I think with
>the original plan, the problem was avoided by always giving full stripe
>writes to the raid layers. �Does the current plan deal with the hol
After converting all my raw images to qcow2 the host no longer
segfaults, but I still get a corrupted btrfs filesystem. Please have a
look at this new image at
http://home.react.nl/~sjon/bug-reports/btrfs/btrfs-corrupt.qcow2.gz
(16 KiB) It contains a 20 GiB disk with 1 partition that btrfsck
(again
On Fri, Feb 08, 2013 at 04:12:17PM -0700, Florian Hofmann wrote:
> I ran it as root. The first times there was no output whatsoever. This
> time triggering gave the SysRq : Show Blocked State line. Strange
>
Well that's weird, it looks like you don't have any blocked tasks, so either
sysrq+w is sc
Each time pick one dead root from the list and let the caller know if
it's needed to continue. This should improve responsiveness during
umount and balance which at some point wait for cleaning all currently
queued dead roots.
A new dead root is added to the end of the list, so the snapshots
disap
On Mon, Feb 11, 2013 at 4:05 PM, Josef Bacik wrote:
> On Fri, Feb 08, 2013 at 04:12:17PM -0700, Florian Hofmann wrote:
>> I ran it as root. The first times there was no output whatsoever. This
>> time triggering gave the SysRq : Show Blocked State line. Strange
>>
>
> Well that's weird, it looks l
On 2/9/13 5:38 PM, David Sterba wrote:
> The defrag operation can take very long, we want to have a way how to
> cancel it. The code checks for a pending signal at safe points in the
> defrag loops and returns EAGAIN. This means a user can press ^C after
> running 'btrfs fi defrag', woks for both d
On Friday 08 February 2013, David Sterba wrote:
> On Mon, Feb 04, 2013 at 09:55:50PM +, Arnd Bergmann wrote:
> > On Saturday 02 February 2013, Chris Mason wrote:
> >
> > I've done a full backup of all data now, without any further Ooops
> > messages, but
> > I did get these:
> >
> > [66155.4
On Mon, Feb 11, 2013 at 10:59:54AM -0600, Eric Sandeen wrote:
> On 2/9/13 5:38 PM, David Sterba wrote:
> > The defrag operation can take very long, we want to have a way how to
> > cancel it. The code checks for a pending signal at safe points in the
> > defrag loops and returns EAGAIN. This means
On 2/11/13 11:45 AM, David Sterba wrote:
> On Mon, Feb 11, 2013 at 10:59:54AM -0600, Eric Sandeen wrote:
>> On 2/9/13 5:38 PM, David Sterba wrote:
>>> The defrag operation can take very long, we want to have a way how to
>>> cancel it. The code checks for a pending signal at safe points in the
>>>
On Mon, Feb 11, 2013 at 11:48:20AM -0600, Eric Sandeen wrote:
> On 2/11/13 11:45 AM, David Sterba wrote:
> > __btrfs_run_defrag_inode -> btrfs_defrag_file applies only in case of
> > autodefrag. The ioctl 'defrag' goes directly to btrfs_defrag_file and
> > what you describe does not happen here.
>
On Thu, Feb 07, 2013 at 11:55:51PM -0700, Miao Xie wrote:
> Here is the whole story:
> Trans_Attach_Task Trans_Commit_Task
> btrfs_commit_transaction()
>|->wait writers to be 1
> btrfs_attach_tra
@Leonidas: I don't think so ... this is running on a i7 core and lzo
is pretty damn fast.
2013/2/11 Leonidas Spyropoulos :
> On Mon, Feb 11, 2013 at 4:05 PM, Josef Bacik wrote:
>> On Fri, Feb 08, 2013 at 04:12:17PM -0700, Florian Hofmann wrote:
>>> I ran it as root. The first times there was no o
On Mon, Feb 11, 2013 at 05:25:58PM +0900, Namjae Jeon wrote:
> From: Namjae Jeon
>
> This patch is a follow up on below patch:
>
> [PATCH] exportfs: add FILEID_INVALID to indicate invalid fid_type
> commit: 216b6cbdcbd86b1db0754d58886b466ae31f5a63
> diff --git a/fs/xfs/xfs_export.c b/fs/xf
2013/2/12, Dave Chinner :
> On Mon, Feb 11, 2013 at 05:25:58PM +0900, Namjae Jeon wrote:
>> From: Namjae Jeon
>>
>> This patch is a follow up on below patch:
>>
>> [PATCH] exportfs: add FILEID_INVALID to indicate invalid fid_type
>> commit: 216b6cbdcbd86b1db0754d58886b466ae31f5a63
>
>> diff -
Hi Florian,
On 10/02/13 00:35, Florian Hofmann wrote:
> (Sadly) No SSD.
I think Marc was asking as they can cause issues, so don't be sad. :-)
> I just upgraded from kernel version 3.7.5 to 3.7.6 (running Arch
> Linux) with no change in behavior.
There are rarely any updates to btrfs in stable
Currently, the following commands succeed.
# cat /proc/swaps
FilenameTypeSizeUsed
Priority
/dev/sda3 partition 8388604 0 -1
/dev/sdc8 partition 9765884 0 -2
On 2/11/13 7:25 PM, Tsutomu Itoh wrote:
> Currently, the following commands succeed.
>
> # cat /proc/swaps
> FilenameTypeSizeUsed
> Priority
> /dev/sda3 partition 8388604 0 -1
> /dev/sdc8
Hi, Eric,
Thanks for your comment.
On 2013/02/12 13:22, Eric Sandeen wrote:
On 2/11/13 7:25 PM, Tsutomu Itoh wrote:
Currently, the following commands succeed.
# cat /proc/swaps
FilenameTypeSizeUsed
Priority
/dev/sda3
Also immediately after this problem, its impossible to mount the
filesystem. it consistently fails with
[ 2092.254428] BUG: unable to handle kernel NULL pointer dereference
at 03c4
[ 2092.255945] IP: []
btrfs_search_old_slot+0x63e/0x940 [btrfs]
[ 2092.257340] PGD 23d42067 PUD 3a93a067
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/6/13 11:02 AM, Liu Bo wrote:
> On Wed, Feb 06, 2013 at 09:53:05AM -0600, Eric Sandeen wrote:
>> On 2/5/13 8:08 PM, Liu Bo wrote:
>>> On Tue, Feb 05, 2013 at 03:14:05PM -0800, Zach Brown wrote:
> + struct btrfs_inode *b_inode = BTRFS_I(inode);
31 matches
Mail list logo
