On 25 September 2015 at 15:51, Hugo Mills wrote:
> On Fri, Sep 25, 2015 at 03:36:18PM +0200, Sjoerd wrote:
>> Thanks all for the feedback. Still doubting though to go for 4.2.1 or not.
>> Main reason is that I am currently running 4.1.7 on my laptop which seems to
>> work fine
net> wrote:
> On Fri, Sep 25, 2015 at 9:25 AM, Bostjan Skufca <bost...@a2o.si> wrote:
>>
>> Similar here: I am sticking with 3.19.2 which has proven to work fine for me
>
> I'd recommend still tracking SOME stable series. I'm sure there were
> fixes in 3.19 for btrfs
Could please someone comment on this, especially whether I am on
somewhat correct course, or did I completely miss the interpretation
of btrfs-debug-tree output values? :)
Thank you very much in advance,
b.
On 21 August 2015 at 23:18, Bostjan Skufca bost...@a2o.si wrote:
Hi Duncan,
tnx
wrote:
Bostjan Skufca posted on Fri, 21 Aug 2015 17:49:01 +0200 as excerpted:
is there a way to get information about how much space is occupied in
each chunk?
In the end, a simple ascii chart of usage distribution should be
preferable, but I can work towards that if there is a way to get
Anyone?
On 18 September 2010 01:33, Bostjan Skufca bost...@a2o.si wrote:
Hi all!
I was looking into some custom fileserver options and noticed two
facts about ZFS - support for L2ARC (albeit not persistant across
reboots, which is a downer) and OpenSolaris being a dead meat. Then I
found
Hi all!
I was looking into some custom fileserver options and noticed two
facts about ZFS - support for L2ARC (albeit not persistant across
reboots, which is a downer) and OpenSolaris being a dead meat. Then I
found out that some patches were already floating around linux
mailinglists, patches