附件显示乱码，请点预览查看<>
This patch adds per-super attributes to sysfs.
It doesn't publish any attributes yet, but does the proper lifetime
handling as well as the basic infrastructure to add new attributes.
Signed-off-by: Jeff Mahoney
---
fs/btrfs/ctree.h |2 ++
fs/btrfs/disk-io.c |9 +
fs/btrfs/sysf
This patch adds the ability to change (set/clear) features while the file
system is mounted. A bitmask is added for each feature set for the
support to set and clear the bits. A message indicating which bit
has been set or cleared is issued when it's been changed and also when
permission or support
While trying to debug ENOSPC issues, it's helpful to understand what the
kernel's view of the available space is. We export this information
via ioctl, but sysfs files are more easily used.
Signed-off-by: Jeff Mahoney
---
fs/btrfs/ctree.h |5 +
fs/btrfs/extent-tree.c | 82 +++
btrfs filesystem df output will show the size of the metadata space
and how much of it is used, and the user assumes that the difference
is all usable space. Since that's not actually the case due to the
global metadata reservation, we should provide the full picture to the
user.
This patch adds a
Now that we have the feature name strings available in the kernel via
the sysfs attributes, we can use them for printing better failure
messages from the ioctl path.
Signed-off-by: Jeff Mahoney
---
fs/btrfs/ioctl.c | 35 ++-
fs/btrfs/sysfs.c | 33 +
This patch publishes information on which features are enabled in the
file system on a per-super basis. At this point, it only publishes
information on features supported by the file system implementation.
Signed-off-by: Jeff Mahoney
---
fs/btrfs/sysfs.c | 81 ++
This patch adds the ability to publish supported features to sysfs under
/sys/fs/btrfs/features.
The files are module-wide and export which features the kernel supports.
The content, for now, is just "0\n".
Signed-off-by: Jeff Mahoney
---
fs/btrfs/sysfs.c | 44 +++
Now that we have the infrastructure for per-super attributes, we can
publish device membership in /sys/fs/btrfs//devices. The information
is published as symlinks to the block devices.
Signed-off-by: Jeff Mahoney
---
fs/btrfs/ctree.h |1 +
fs/btrfs/sysfs.c | 32
There are some feature bits that require no offline setup and can
be enabled online. I've only reviewed extended irefs, but there will
probably be more.
We introduce three new ioctls:
- BTRFS_IOC_GET_SUPPORTED_FEATURES: query the kernel for supported features.
- BTRFS_IOC_GET_FEATURES: query the k
This adds a writeable attribute which describes the label.
Signed-off-by: Jeff Mahoney
---
fs/btrfs/sysfs.c | 44
1 file changed, 44 insertions(+)
--- a/fs/btrfs/sysfs.c 2013-10-21 16:20:06.395804741 -0400
+++ b/fs/btrfs/sysfs.c 2013-10-21 16:23:
With the compat and compat-ro bits, it's possible for file systems to
exist that have features that aren't supported by the kernel's file system
implementation yet still be mountable.
This patch publishes read-only info on those features using a prefix:number
format, where the number is the bit nu
struct kobj_attribute implements the baseline attribute functionality
that can be used all over the place. We should export the ops associated
with it.
Signed-off-by: Jeff Mahoney
Signed-off-by: Greg Kroah-Hartman
---
lib/kobject.c |1 +
1 file changed, 1 insertion(+)
--- a/lib/kobject.c
When debugging ENOSPC issues, it's nice to be able to see which
reservations failed as well as the ones which succeeded.
Signed-off-by: Jeff Mahoney
---
fs/btrfs/extent-tree.c |7 +++
1 file changed, 7 insertions(+)
--- a/fs/btrfs/extent-tree.c2013-11-03 16:53:15.466324826 -0500
+++
This patchset implements the stubbed-out sysfs interface for btrfs. Or
at least begins to do so.
We publish:
- Features supported by the file system implementation
- Features enabled on the file system, including features unknown to
the implemenation. These attributes can also be used to enable
On Thu, Nov 07, 2013 at 02:25:50AM +0530, Himangi Saraogi wrote:
> This patch replaces kmalloc(size * nr, ) with kmalloc_array(nr, size)
> as kmalloc_array() is preferred because it can check that the
> calculation doesn't wrap and won't return a smaller allocation.
> Also kzalloc(size * nr) was re
On Sun, Nov 10, 2013 at 12:39:32PM +0100, Valentina Giusti wrote:
> This patch fixes the following warnings:
> fs/btrfs/transaction.c: In function ‘wait_for_commit’:
> fs/btrfs/transaction.c:560:57: warning: unused parameter ‘root’
> [-Wunused-parameter]
> fs/btrfs/transaction.c: In function ‘btrf
We have no tests for testing qgroups, so we have no way of knowing if our
changes are breaking qgroups at all. Get the ball rolling with some basic
functionality tests, these just make sure we can enable quotas and do rescan and
get sane values back, as well as make sure the limiting stuff works p
Btrfs had some issues with fsync()'ing directories and fsync()'ing after
renames. These three new tests cover the 3 different issues we were seeing.
This breaks out the dmflakey stuff into a common helper to be shared between
generic/311 and generic/321. Thanks,
Signed-off-by: Josef Bacik
---
V1
Btrfs was screwing up rename+fsync, add some regression tests for the various
scenarios it was screwing up. Thanks,
Signed-off-by: Josef Bacik
---
tests/generic/322 | 111 ++
tests/generic/322.out | 7
tests/generic/group | 1 +
3 f
Another two days and a backtrace shows the hope of progress:
#0 0x0041de2f in btrfs_node_key ()
#1 0x0041ee79 in btrfs_check_node ()
#2 0x00420211 in check_block ()
#3 0x00420813 in btrfs_search_slot ()
#4 0x00427bb4 in btrfs_read_block_groups ()
#5 0x
On Fri, Nov 15, 2013 at 9:27 AM, Hugo Mills wrote:
> On Fri, Nov 15, 2013 at 02:33:58PM +, Alin Dobre wrote:
>> We are using btrfs filesystems in our infrastructure and, at some
>> point of time, they start refusing to create new subvolumes.
>>
>> Each file system is being quota initialized im
On Fri, Nov 15, 2013 at 4:19 PM, Chris Mason wrote:
> Chris Mason (1) commits (+7/-2):
> btrfs: fix empty_zero_page misusage
https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?h=for-linus&id=46e0f66a0cf9e1fe25bfdcf4a60c08aface85998
FYI, you may want to loop over longs
Alin Dobre posted on Fri, 15 Nov 2013 14:33:58 + as excerpted:
> We are using btrfs filesystems in our infrastructure and, at some point
> of time, they start refusing to create new subvolumes.
>
> Each file system is being quota initialized immediately after its
> creation
I'd suggest stayi
On Fri, Nov 15, 2013 at 02:33:58PM +, Alin Dobre wrote:
> We are using btrfs filesystems in our infrastructure and, at some
> point of time, they start refusing to create new subvolumes.
>
> Each file system is being quota initialized immediately after its
> creation (with "btrfs quota enable"
Hi Linus,
This pull fixes the empty_zero_page bug that Heiko reported, and
includes one more cleanup from Al Viro. Please grab my for-linus:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Chris Mason (1) commits (+7/-2):
btrfs: fix empty_zero_page misusage
A
On Fri, Nov 15, 2013 at 07:25:33PM +0800, Anand Jain wrote:
> need fsinfo from btrfs-control that is when mount path is
> not known.
> current method of going through each mount points isn't
> efficient, and multiple subvol of a fsid could be mounted
> means extra logic to handle that. Further this
Hello,
We are using btrfs filesystems in our infrastructure and, at some point
of time, they start refusing to create new subvolumes.
Each file system is being quota initialized immediately after its
creation (with "btrfs quota enable") and then all subfolders under the
root directory are cr
Hugo Mills posted on Fri, 15 Nov 2013 12:38:41 + as excerpted:
>> I also wonder: Would btrfs try to write _two_ copies of everything to
>> _one_ remaining device of a degraded two-disk raid1?
>
> No. It would have to degrade from RAID-1 to DUP to do that (and I
> think we prevent DUP data for
On Fri, Nov 15, 2013 at 02:42:08PM +0100, Geert Uytterhoeven wrote:
> On Fri, Nov 15, 2013 at 2:40 PM, Chris Mason wrote:
> > Quoting Chris Mason (2013-11-15 07:21:31)
> >> Quoting Heiko Carstens (2013-11-15 06:32:16)
> >> > On Thu, Nov 14, 2013 at 12:19:52PM -0500, Chris Mason wrote:
> >> > > Hi
On Fri, Nov 15, 2013 at 11:29:36AM +0100, Goffredo Baroncelli wrote:
> Add the ERROR prefix to the error messages of mkfs, to align it
> to the btrfs main utility style.
>
> The patch increase the buffer size of test_dev_for_mkfs() and
> test_num_disk_vs_raid() for the error message from 100 to 15
On Fri, Nov 15, 2013 at 2:40 PM, Chris Mason wrote:
> Quoting Chris Mason (2013-11-15 07:21:31)
>> Quoting Heiko Carstens (2013-11-15 06:32:16)
>> > On Thu, Nov 14, 2013 at 12:19:52PM -0500, Chris Mason wrote:
>> > > Hi Linus,
>> > >
>> > > Please pull my for-linus branch:
>> > >
>> > > git://git.
Quoting Chris Mason (2013-11-15 07:21:31)
> Quoting Heiko Carstens (2013-11-15 06:32:16)
> > On Thu, Nov 14, 2013 at 12:19:52PM -0500, Chris Mason wrote:
> > > Hi Linus,
> > >
> > > Please pull my for-linus branch:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
>
On Fri, Nov 15, 2013 at 12:31:24PM +0100, Lutz Vieweg wrote:
> Hi again,
>
> I just did another test on resilience with btrfs/raid1, this time I tested
> the following scenario: One out of two raid1 devices disappears. The
> filesystem
> is written to in degraded mode. The missing device re-appea
Quoting Heiko Carstens (2013-11-15 06:32:16)
> On Thu, Nov 14, 2013 at 12:19:52PM -0500, Chris Mason wrote:
> > Hi Linus,
> >
> > Please pull my for-linus branch:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
> > for-linus
> >
> > This is our usual merge window set
On Thu, Nov 14, 2013 at 12:19:52PM -0500, Chris Mason wrote:
> Hi Linus,
>
> Please pull my for-linus branch:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
>
> This is our usual merge window set of bug fixes, performance
> improvements and cleanups. Miao Xie
Hi again,
I just did another test on resilience with btrfs/raid1, this time I tested
the following scenario: One out of two raid1 devices disappears. The filesystem
is written to in degraded mode. The missing device re-appears (think of e.g.
a storage device that temporarily became unavailable du
Quoting Anand Jain (2013-11-15 06:11:09)
> This fixes the regression introduced with the patch
>
> btrfs-progs: avoid write to the disk before sure to create fs
>
> what happened with this patch is it missed the check to see if the
> user has the option set before pushing the defaults.
Thank
need fsinfo from btrfs-control that is when mount path is
not known.
current method of going through each mount points isn't
efficient, and multiple subvol of a fsid could be mounted
means extra logic to handle that. Further this will help
to revamp check_mounted() (planned)
check_mounted is heavi
as of now with out this patch user would see
fsinfo per btrfs mount path but which mean multiple
entry if more than one subvol is mounted of the same
fsid. so this patch will handle that nicely.
Signed-off-by: Anand Jain
---
v4: rebase on integration-20131114
v3: accepts Josef suggested
v2: acce
A new test case when disk is unmounted and if the non mapper
disk path is given as the argument to the btrfs filesystem show
we still need this to work but lblkid will pull only mapper disks,
it won't match. So this will normalize the input to find btrfs
by fsid and pass it to the search.
Signed-
This fixes the regression introduced with the patch
btrfs-progs: avoid write to the disk before sure to create fs
what happened with this patch is it missed the check to see if the
user has the option set before pushing the defaults.
Signed-off-by: Anand Jain
---
v2: accepts G.Baroncelli s
On 11/15/2013 05:44 AM, Anand Jain wrote:
Thanks for the test case and heads-up on this. The code missed
the check if the user has provided the option before default
profile for the mixed group (due to small vol) is enforced.
I have sent out the following patch to fix it.
[PATCH] btrfs-
On 11/15/2013 05:44 AM, Anand Jain wrote:
Thanks for the test case and heads-up on this. The code missed
the check if the user has provided the option before default
profile for the mixed group (due to small vol) is enforced.
I have sent out the following patch to fix it.
[PATCH] btrfs-
Add the ERROR prefix to the error messages of mkfs, to align it
to the btrfs main utility style.
The patch increase the buffer size of test_dev_for_mkfs() and
test_num_disk_vs_raid() for the error message from 100 to 150
because the former become too small.
Signed-off-by: Goffredo Baroncelli
--
Prefix with "ERROR:" the error messages of mkfs
Add the ERROR prefix to the error messages of mkfs, to align it
to the btrfs main utility style.
The patch also increase the buffer size of test_dev_for_mkfs() and
test_num_disk_vs_raid() for the error message from 100 to 150
because the former be
Goffredo Baroncelli posted on Fri, 15 Nov 2013 08:30:49 +0100 as
excerpted:
> On 2013-11-15 08:12, Duncan wrote:
>>
> [...]
>>
>> You're saying data+metadata DUP wouldn't be possible here either, which
>> would make me pretty unhappy too.
>
> The problem should be in mkfs.btrfs not in the btrfs
Hugo Mills posted on Thu, 14 Nov 2013 21:00:56 + as excerpted:
>> Is there a formula to calculate how much space btrfs _might_ need?
>
> Not really. I'd expect to need something in the range 250-1500 GiB of
> headroom, depending on the size of the filesystem (and on the size of
> the metadata
There are sometimes other stacktraces, maybe this can help to find the
initil error:
Nov 12 08:11:19 hsad-srv-03 kernel: [ 240.564931] btrfs-transacti D
88063fc72ec0 0 2289 2 0x
Nov 12 08:11:19 hsad-srv-03 kernel: [ 240.564936] 880622d41140
0046 880626
49 matches
Mail list logo
