On Friday, 29 October, 2010, Vladi Gergov wrote:
> kernel: scratch git repo from today 10.29.10 @ 14:30 PST
> Btrfs v0.19-35-g1b444cd-dirty
>
> >>> gypsyops @ /mnt > sudo btrfs filesystem show
> Label: 'das4' uuid: d0e5137f-e5e7-49da-91f6-a9c4e4e72c6f
> Total devices 3 FS bytes used 1.38TB
>
Hi,
> A friend of mine who builds storage systems designed for HPC use
> has been keeping an eye on btrfs and has just done some testing
> of it with 2.6.36 and seems to like what he sees in terms of
> stability.
>
> http://scalability.org/?p=2711
This is nice to see, but we sh
You could always use btrfs filesystem balance progress which would not
introduce a new root level option and still be short to type. That
would mean balance should have a "start" option or default to start
when no sub options are used.
Sent from my mobile device.
On 2010-10-29, at 20:11, Hugo Mil
Add support to the btrfs tool for monitoring a balance operation on a
filesystem.
Signed-off-by: Hugo Mills
---
btrfs.c |4
btrfs_cmds.c | 40
btrfs_cmds.h |1 +
ioctl.h |7 +++
4 files changed, 52 insertions(+)
Index: b
Add an option to the btrfs tool to use the ioctl for cancelling
balance operations.
SIgned-off-by: Hugo Mills
---
btrfs.c |4
btrfs_cmds.c | 41 +
btrfs_cmds.h |1 +
ioctl.h |1 +
4 files changed, 47 insertions(+)
Index: btrf
These two patches complement the previous two kernel-side
patches. The first implements a way of displaying the current progress
of any running balance process. The second patch allows a running
balance to be cancelled.
I'm a bit uncertain about the best name for these commands. Several
opti
These two patches give a degree of control over balance operations.
The first makes it possible to get an idea of how much work remains to
do, by tracking the number of block groups (chunks) that need to be
moved/rewritten. The second patch allows a running balance operation
to be cancelled when
This patch introduces a basic form of progress monitoring for balance
operations, by counting the number of block groups remaining. The
information is exposed to userspace by an ioctl.
Signed-off-by: Hugo Mills
---
fs/btrfs/ctree.h |9
fs/btrfs/disk-io.c |2 +
fs/btrfs/ioctl.
This patch adds an ioctl for cancelling a btrfs balance operation
mid-flight. The ioctl simply sets a flag, and the operation terminates
after the current block group move has completed.
Signed-off-by: Hugo Mills
---
fs/btrfs/ctree.h |1 +
fs/btrfs/ioctl.c | 25 +++
A friend of mine who builds storage systems designed for HPC
use has been keeping an eye on btrfs and has just done some
testing of it with 2.6.36 and seems to like what he sees in
terms of stability.
http://scalability.org/?p=2711
# But it passed our stability test. 100 iterations (3.2TB
# writt
kernel: scratch git repo from today 10.29.10 @ 14:30 PST
Btrfs v0.19-35-g1b444cd-dirty
>>> gypsyops @ /mnt > sudo btrfs filesystem show
Label: 'das4' uuid: d0e5137f-e5e7-49da-91f6-a9c4e4e72c6f
Total devices 3 FS bytes used 1.38TB
devid3 size 1.82TB used 0.00 path /dev/sdb
devid
So, I ended up just applying the relevant commit to my existing source
tree, which did allow me to successfully remove the missing drive, so
I seem to be back up and running.
Thank you very much!
-- Erik
On Thu, Oct 28, 2010 at 1:57 PM, Chris Mason wrote:
>
> On Tue, Oct 19, 2010 at 07:17:16PM
12 matches
Mail list logo
