Heyho!
(This is using btrfs from Debian's 2.6.32 2.6.32-3-kirkwood kernel (-9
package; btrfs tools is v0.19-16-g075587c)
A few observations about btrfsck:
a btrfsck run on a 2T volume (4 disks) on a QNAP appliance (512M ram) got
killed by Mr. OOM Killer. Initially, I was quite
on the laptop.)
cheers
-- vbi
On Thursday 27 May 2010 20.15:53 Josef Bacik wrote:
On Thu, May 27, 2010 at 06:46:04PM +0200, Adrian von Bidder wrote:
Heyho!
(This is using btrfs from Debian's 2.6.32 2.6.32-3-kirkwood kernel (-9
package; btrfs tools is v0.19-16-g075587c)
A few observations
Hi,
I like this very much, I found myself wondering which program did what again
and again when I started to use btrfs, too.
On Thursday 21 January 2010 20.29:26 Goffredo Baroncelli wrote:
btrfs resize|-r [+/-]newsize[gkm]|max filesystem
Resize the file system. If 'max'
Heyho!
On Thursday 14 January 2010 02.08:29 Chris Mason wrote:
On Mon, Jan 11, 2010 at 09:45:31AM +0100, Adrian von Bidder wrote:
On Monday 11 January 2010 08.34:36 Adrian von Bidder wrote:
btrfs-vol -b on an 2T btrfs fs (raid 1 mode over 4 disks) on an arm
CPU has triggered it several
Hi,
On Tuesday 12 January 2010 08.08:26 Piavlo wrote:
Maintaining snapshot hierarchy by external application is not reliable
and error prone
compared to maintaining it withing the btrfs itself,
probably by adding the parent treeid field for every shapshot/subvolume.
What should, in your
On Sunday 10 January 2010 21.05:46 Johannes Hirte wrote:
I've observed this hanging task now several times. Not sure when this
started, but 2.6.32 is affected too, IIRC. I don't have a test pattern
for this. Dovecot imap triggers this from time to time. I've enabled
CONFIG_DETECT_HUNG_TASK
On Tuesday 12 January 2010 03.19:34 TARUISI Hiroaki wrote:
In btrfs, snapshot is a clone of subvolume, not arbitrary
directory.
You specified '/root' directory and it is not subvolume,
snapshot is created for parent subvolume, root of filesystem.
... hence my proposal (haven't seen a comment
On Wednesday 06 January 2010 01.30:35 TARUISI Hiroaki wrote:
In creating snapshots, the last argument implies the directory
where subvolume is to be created, but in taking snapshots,
the last argument implies subvolume we take snapshot of, and
snapshots are created under current directory.
On Thursday 31 December 2009 21.44:58 regomodo wrote:
On Thursday 31 December 2009 19:24:12 Chris Ball wrote:
Hi Reg,
Hi, I have a btrfs 'pool' of x2 Samsung 500GB HDD's in non-raid
format. It works fine for the most part except for mounting on
bootup. Every bootup I have to
Heyho!
I'm currently (once more) trying to experiment with btrfs, especially since
the ENOSPC handling and delete snapshots/subvolumes make it look extremely
appealing now.
Some questions:
* how do I list available snapshots/subvolumes?
* assuming a disk has failed: just to be sure:
Heyho!
Just a first impression report from a pure user. I've started to play
around with btrfs a bit, without using any btrfs-specific features so far,
though.
700G, ca. 1/2 full, tons of small files, lots of hardlinks (dirvish backup
trees of my workstations at home.)
The disk is currently
11 matches
Mail list logo
