On 2016-11-29 00:06, Duncan wrote:
Niccolò Belli posted on Mon, 28 Nov 2016 12:11:49 +0100 as excerpted:
On lunedì 28 novembre 2016 09:20:15 CET, Kai Krakow wrote:
You can, however, use chattr to make the subvolume root directory (that
one where it is mounted) nodatacow (chattr +C) _before_ pl
On 2016-11-29 00:14, Duncan wrote:
Graham Cobb posted on Mon, 28 Nov 2016 09:49:33 + as excerpted:
On 28/11/16 02:56, Duncan wrote:
It should still be worth turning on autodefrag on an existing somewhat
fragmented filesystem. It just might take some time to defrag files
you do modify, and
On martedì 29 novembre 2016 06:14:18 CET, Duncan wrote:
Very good question that I don't know the answer to as I've not seen it
discussed previously. (I'm not a dev, just a list regular and user of
btrfs myself, and my personal use-case involves neither snapshots nor
send/receive, so on those t
Graham Cobb posted on Mon, 28 Nov 2016 09:49:33 + as excerpted:
> On 28/11/16 02:56, Duncan wrote:
>> It should still be worth turning on autodefrag on an existing somewhat
>> fragmented filesystem. It just might take some time to defrag files
>> you do modify, and won't touch those you don't
Niccolò Belli posted on Mon, 28 Nov 2016 12:11:49 +0100 as excerpted:
> On lunedì 28 novembre 2016 09:20:15 CET, Kai Krakow wrote:
>> You can, however, use chattr to make the subvolume root directory (that
>> one where it is mounted) nodatacow (chattr +C) _before_ placing any
>> files or directori
On lunedì 28 novembre 2016 09:20:15 CET, Kai Krakow wrote:
You can, however, use chattr to make the subvolume root directory (that
one where it is mounted) nodatacow (chattr +C) _before_ placing any
files or directories in there. That way, newly created files and
directories will inherit the flag
On 28/11/16 02:56, Duncan wrote:
> It should still be worth turning on autodefrag on an existing somewhat
> fragmented filesystem. It just might take some time to defrag files you
> do modify, and won't touch those you don't, which in some cases might
> make it worth defragging those manually.
Am Mon, 28 Nov 2016 01:38:29 +0100
schrieb Ulli Horlacher :
> On Sat 2016-11-26 (11:27), Kai Krakow wrote:
>
> > > I have vmware and virtualbox VMs on btrfs SSD.
>
> > As a side note: I don't think you can use "nodatacow" just for one
> > subvolume while the other subvolumes of the same btrfs
Ulli Horlacher posted on Mon, 28 Nov 2016 01:38:29 +0100 as excerpted:
> Ok, then next question :-)
>
> What is better (for a single user workstation): using mount option
> "autodefrag" or call "btrfs filesystem defragment -r" (-t ?) via nightly
> cronjob?
>
> So far, I use neither.
First point
On Sat 2016-11-26 (11:27), Kai Krakow wrote:
> > I have vmware and virtualbox VMs on btrfs SSD.
> As a side note: I don't think you can use "nodatacow" just for one
> subvolume while the other subvolumes of the same btrfs are mounted
> different. The wiki is just wrong here.
>
> The list of poss
Am Fri, 25 Nov 2016 09:28:40 +0100
schrieb Ulli Horlacher :
> I have vmware and virtualbox VMs on btrfs SSD.
>
> I read in
> https://btrfs.wiki.kernel.org/index.php/SysadminGuide#When_To_Make_Subvolumes
>
> certain types of data (databases, VM images and similar
> typically big files that a
On Fri, 25 Nov 2016 12:01:37 + (UTC)
Duncan <1i5t5.dun...@cox.net> wrote:
> Obviously this can be a HUGE problem on spinning rust due to its seek times,
> a problem zero-seek-time ssds don't have
They are not strictly zero seek time either. Sure you don't have the issue of
moving the physical
Ulli Horlacher posted on Fri, 25 Nov 2016 09:28:40 +0100 as excerpted:
> I have vmware and virtualbox VMs on btrfs SSD.
>
> I read in
> https://btrfs.wiki.kernel.org/index.php/SysadminGuide
#When_To_Make_Subvolumes
>
> certain types of data (databases, VM images and similar typically
>
I have vmware and virtualbox VMs on btrfs SSD.
I read in
https://btrfs.wiki.kernel.org/index.php/SysadminGuide#When_To_Make_Subvolumes
certain types of data (databases, VM images and similar typically big
files that are randomly written internally) may require CoW to be
disabled fo
14 matches
Mail list logo