From: Filipe Manana
If readpages() (triggered by defrag or buffered reads) is called while a
direct IO write is in progress, we have a small time window where we can
deadlock, resulting in traces like the following being generated:
[84723.212993] INFO: task fio:2849 blocked
Hi Filipe,
[auto build test ERROR on v4.4-rc4]
[also build test ERROR on next-20151208]
[cannot apply to btrfs/next]
url:
https://github.com/0day-ci/linux/commits/fdmanana-kernel-org/Btrfs-fix-leaking-of-ordered-extents-after-direct-IO-write-error/20151209-182927
config: x86_64-randconfig
Alistair Grant posted on Wed, 09 Dec 2015 09:38:47 +1100 as excerpted:
> On Tue, Dec 08, 2015 at 03:25:14PM +, Duncan wrote:
>> Alistair Grant posted on Tue, 08 Dec 2015 06:55:04 +1100 as excerpted:
>>
>> > On Mon, Dec 07, 2015 at 01:48:47PM +, Duncan wrote:
>> >> Alistair Grant posted
From: Filipe Manana
When doing a direct IO write, __blockdev_direct_IO() can call the
btrfs_get_blocks_direct() callback one or more times before it calls the
btrfs_submit_direct() callback. However it can fail after calling the
first callback and before calling the second
Christoph Anton Mitterer posted on Wed, 09 Dec 2015 05:36:37 +0100 as
excerpted:
> On Fri, 2015-11-27 at 01:02 +, Duncan wrote:
> [snip snap]
>> #2 The point I was trying to make, now, to mount it you'll mount not a
>> native nested subvol, and not a directly available sibling
>>
Christoph Anton Mitterer posted on Wed, 09 Dec 2015 05:38:02 +0100 as
excerpted:
> On Fri, 2015-11-27 at 02:02 +, Duncan wrote:
>> Consider a setuid-root binary with a recently publicized but patched on
>> your system vuln. But if you have root snapshots from before the patch
>> and those
a-kernel-org/Btrfs-fix-leaking-of-ordered-extents-after-direct-IO-write-error/20151209-182927
> config: x86_64-randconfig-x008-12090811 (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (n
Can anyone help me with this question?
Not only the kernel space API freeze_bdev, but also the IO control which can be
called from user space.
-Original Message-
From: Wang, Zhiye
Sent: Saturday, December 5, 2015 5:57 PM
To: linux-btrfs@vger.kernel.org
Subject: freeze_bdev and
Hi,
Trying to run a balance on a filesystem results in the below dmesg output.
Kernel is 4.1.13 from kernel.org.
System is running in AWS (hence the Xen stuff).
INFO: task btrfs:28938 blocked for more than 120 seconds.
Not tainted 4.1.13-dg1 #1
"echo 0 >
Christoph Anton Mitterer posted on Wed, 09 Dec 2015 06:07:38 +0100 as
excerpted:
> Well as I've said, getting that in via USB may be only one way.
> We're already so far that GNOME automount devices when plugged...
Ugh. ... And many know that's the sort of thing that made MS so much of
a
Christoph Anton Mitterer posted on Wed, 09 Dec 2015 06:43:01 +0100 as
excerpted:
> Hey Hugo,
>
>
> On Thu, 2015-11-26 at 00:33 +, Hugo Mills wrote:
>
>> The issue is that nodatacow bypasses the transactional nature of
>> the FS, making changes to live data immediately. This then means that
On 2015-11-27 03:02, Duncan wrote:
>>> Then there's the security angle to consider. With the (basically,
>>> possibly modified as I suggested) flat layout, mounting something
>>> doesn't automatically give people in-tree access to nested subvolumes
>>> (subject to normal file permissions, of
Christoph Anton Mitterer posted on Wed, 09 Dec 2015 06:45:47 +0100 as
excerpted:
> On 2015-11-27 00:08, Duncan wrote:
>> Christoph Anton Mitterer posted on Thu, 26 Nov 2015 01:23:59 +0100 as
>> excerpted:
>>> 1) AFAIU, the fragmentation problem exists especially for those files
>>> that see many
On Sat, Dec 05, 2015 at 09:57:18AM +, Wang, Zhiye wrote:
> Hi all,
>
>
> If I understand it correctly, defragment operation is done in user space
> tools, while scrub/re-balance is done in kernel thread.
Defragment is done via a IOCTL, so it also works in the kernel.
>
>
> So, if my
On 2015-12-09 05:53, Duncan wrote:
> Christoph Anton Mitterer posted on Wed, 09 Dec 2015 05:36:37 +0100 as
> excerpted:
>
>> On Fri, 2015-11-27 at 01:02 +, Duncan wrote:
>> [snip snap]
>>> #2 The point I was trying to make, now, to mount it you'll mount not a
>>> native nested subvol, and not
On Wed, 2015-12-09 at 16:48 +, Duncan wrote:
> David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
>
> > Seems I need to upgrade my tools. That command was added in 3.18 and I
> > only have the 3.12 tools.
>
> Definitely so, especially because you're running raid6, which
On Thu, Dec 03, 2015 at 12:59:50PM +0100, Christoph Hellwig wrote:
> The btrfs clone ioctls are now adopted by other file systems, with NFS
> and CIFS already having support for them, and XFS being under active
> development. To avoid growth of various slightly incompatible
> implementations, add
mi-tse,
wie sieht's aus, haste den File runtergeladen?
S-li
--
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
This is a Mythbuntu system, and the latest they support is 14.04.
Thanks for all the responses.
David
On Thu, 2015-12-10 at 06:56 +1100, Gareth Pye wrote:
> I wouldn't blame Ubuntu too much, 14.10 went out of support months ago
> (which counts as a long time when it's only for people happy to
On Tue, Dec 08, 2015 at 03:26:41PM +0800, Zhao Lei wrote:
> Hi, Dave Chinner
>
> > -Original Message-
> > From: Dave Chinner [mailto:da...@fromorbit.com]
> > Sent: Tuesday, December 08, 2015 6:12 AM
> > To: Zhaolei
> > Cc: fste...@vger.kernel.org;
Ubuntu 14.04 actually ships with the 3.13 kernel. I had already
upgraded it to 3.19 from the Ubuntu 15.04 release.
I'm pretty sure I created the btrfs partition, not the MythBuntu
installer. I don't remember if that was even an option.
David
On Wed, 2015-12-09 at 14:28 -0700, Chris Murphy
1. better practices, we really need to tell users, and documentation
writers, that using dd (or variant) to copy Btrfs volumes has a
consequence and should not be used to make copies.
2. Btrfs needs a better way to make a copy of a volume when there are
snapshots (including even rw snapshots);
On Wed, Dec 9, 2015 at 12:56 PM, Gareth Pye wrote:
> I wouldn't blame Ubuntu too much, 14.10 went out of support months ago
OP reported 3.19.0-32-generic #37~14.04.1-Ubuntu. And 14.04 is LTS
supported until 2019. I think it should have something newer for both
kernel and
zieg...@uni-freiburg.de writes:
> mi-tse,
>
> wie sieht's aus, haste den File runtergeladen?
>
> S-li
Huh?
Luis
--
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
Sorry his message 4 hours ago mentioned 14.10.
On Thu, Dec 10, 2015 at 8:41 AM, David Hampton
wrote:
> Ubuntu 14.04 actually ships with the 3.13 kernel. I had already
> upgraded it to 3.19 from the Ubuntu 15.04 release.
>
> I'm pretty sure I created the btrfs
kernel BUG at fs/btrfs/extent-tree.c:1833!
We got this fixed in 4.4-rc1:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2c3cf7d5f6105bb957df125dfce61d4483b8742d
On Wed, Dec 9, 2015 at 11:05 PM, Gerald Hopf wrote:
>
>>> kernel BUG at fs/btrfs/extent-tree.c:1833!
>>
>> We got this fixed in 4.4-rc1:
>>
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2c3cf7d5f6105bb957df125dfce61d4483b8742d
>>
>>
On Wed, Dec 09, 2015 at 11:29:48PM +, Filipe Manana wrote:
> On Wed, Dec 9, 2015 at 11:05 PM, Gerald Hopf
> wrote:
> >
> >>> kernel BUG at fs/btrfs/extent-tree.c:1833!
> >>
> >> We got this fixed in 4.4-rc1:
> >>
> >>
> >>
Chandan Rajendra wrote on 2015/12/08 15:36 +0530:
On Tuesday 08 Dec 2015 14:10:33 Qu Wenruo wrote:
Introduce a new mount option "nologreplay" to co-operate with "ro" mount
option to get real readonly mount, like "norecovery" in ext* and xfs.
Since the new parse_options() need to check new
Introduce a new mount option "nologreplay" to co-operate with "ro" mount
option to get real readonly mount, like "norecovery" in ext* and xfs.
Since the new parse_options() need to check new flags at remount time,
so add a new parameter for parse_options().
Signed-off-by: Qu Wenruo
On Wed, Dec 9, 2015 at 10:28 AM, David Hampton
wrote:
> On Wed, 2015-12-09 at 16:48 +, Duncan wrote:
>> David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
>>
>> > Seems I need to upgrade my tools. That command was added in 3.18 and I
>> > only
I wouldn't blame Ubuntu too much, 14.10 went out of support months ago
(which counts as a long time when it's only for people happy to
upgrade every 6 months).
The kernel ppa's builds tend to run fine on the latest LTS & regular
releases, although they can cause issues (I've had some fun with
David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
> Seems I need to upgrade my tools. That command was added in 3.18 and I
> only have the 3.12 tools.
Definitely so, especially because you're running raid6, which wasn't
stable until 4.1 for both kernel and userspace. 3.12?
33 matches
Mail list logo