> then I do : mount -o rw,remount /backup/
>
> Feb 1 22:32:38 frozen kernel: [ 65.780686] btrfs: force zlib compression
> Feb 1 22:32:38 frozen kernel: [ 65.780700] btrfs: not using ssd allocation
> scheme
> Feb 1 22:32:38 frozen kernel: [ 65.780706] btrfs: disk space caching is
> enable
Hi,
I have a btrfs volume that I can't mount RW (but I can mount and use it
RO).
So, at boot time, the partition is mounted RO
(defaults,noatime,compress-force=zlib,nossd,ro) :
Feb 1 22:30:12 frozen kernel: [8.646350] Btrfs loaded
Feb 1 22:30:12 frozen kernel: [8.650878] device fsid
Dave sent me a panic where we were doing the orphan cleanup and panic'ed
trying to release our reservation from the orphan block rsv. The reason for
this is because our orphan block rsv had been free'd out from underneath us
because the transaction commit found that there were no orphan inodes
acc
Am Donnerstag, 31. Januar 2013 schrieb Hugo Mills:
> On Thu, Jan 31, 2013 at 02:44:12PM +0100, Martin Steigerwald wrote:
> > Hi!
> >
> > Today I converted my /home from Ext4 to BTRFS by reformatting and copying
> > all over again.
> >
> > I created the filesystem with -l 16384 -n 16384 -d single
Instead of doing a BUG_ON() if we fail to find the last fs root just return
an error so the callers can deal with it how they like. Also we need to
actually return an error if we can't find the latest root so that the error
handling works. With this btrfsck was able to deal with a file system tha
Noticed this while looking for an segfault related to our eb cache in
btrfsck. We free the eb in out: so we don't need this extra free. Thanks,
Signed-off-by: Josef Bacik
---
btrfsck.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/btrfsck.c b/btrfsck.c
index ff2d7b5.
A user had a problem where btrfsck would bail out because it was finding
extents for a snapshot that had been deleted but not entirely cleaned up.
We can handle this case fine, we just need to report an error properly.
This patch allowed btrfsck to continue and eventually fix his file system.
Thank
On Thu, Jan 31, 2013 at 08:17:13PM +0100, Martin Steigerwald wrote:
> Hope the extended free space information stuff by Goffredo comes next :)
The code needs some work, and I'm not sure where the dicusssions about
the visual appearance of the output ended. I don't remember whether we
had a general
Hi,
documentation updates, mkfs support of extended refs (aka more hardlinks
possible), new command 'subvolume show' and extensions/updates to
the 'subvolume list' command and fsck fixes.
Please consider this more like a preview, there were some merge
conflicts and I may have missed some combinat
This was a bug from long time ago that never actually got fixed. We start
with bytenr 0 when looping through all of the block groups, but
btrfs_lookup_block_group will bail out since it couldn't find a block group
with 0 as the bytenr. Btrfs_lookup_first_block_group will be nice and
adjust the st
Hello,
Trying to convert degraded raid1 to single...
# mount btrfs0.img /mnt/test -oloop,degraded
# btrfs filesystem balance start -mconvert=single -dconvert=single -f
/mnt/test
...ends up with:
Btrfs v0.20-rc1-56-g6cd836d
device fsid 88c73405-12f4-4dc8-90f2-71925867d0c5 devid 1 transid 4
/
On Thu, Jan 31, 2013 at 10:56:34PM -0700, Miao Xie wrote:
> On Thu, 31 Jan 2013 11:40:41 -0500, Josef Bacik wrote:
> > On Thu, Jan 31, 2013 at 02:23:19AM -0700, Miao Xie wrote:
> >> Currently, we can do unlocked dio reads, but the following race
> >> is possible:
> >>
> >> dio_read_task
subscribe
--
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
On Thu, Jan 31, 2013 at 01:25:26PM -0500, Norbert Veber wrote:
> On Thu, Jan 31, 2013 at 06:34:04PM +0100, David Sterba wrote:
> > Otherwise, Mark's patches add the incompat bit unconditionally, we need
> > a way how to make it tunable in the same way as other mkfs do. I'd say
> > to take them as-i
On Fri, Feb 01, 2013 at 10:58:33AM +0800, Chen Yang wrote:
> > Good catch, thanks. I see that there's no special handling of the '-'
> > filename that usually means stdout. We may want to add this as a common
> > command line usage pattern.
> >
> We can touch a file name "-", so I think special ha
On Fri, Feb 01, 2013 at 09:59:49AM +, Audrius Butkevicius wrote:
> Add '-b' and '--bytes' options to btrfs filesystem df and show, for easier
> integration with scripts. This causes all sizes to be displayed in decimal
> bytes instead of pretty-printed with human-readable suffices KB, MB, etc.
Add '-b' and '--bytes' options to btrfs filesystem df and show, for easier
integration with scripts. This causes all sizes to be displayed in decimal
bytes instead of pretty-printed with human-readable suffices KB, MB, etc.
Signed-off-by: Audrius Butkevicius
---
cmds-filesystem.c | 93
17 matches
Mail list logo