unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Paul Jewell <paul@teulu.org>
To: help-guix@gnu.org
Subject: Re: Running Out of Inodes
Date: Fri, 19 Nov 2021 19:09:28 +0000	[thread overview]
Message-ID: <72502e63-f7c7-cfb9-ee1b-90b3c10ff3a7@teulu.org> (raw)
In-Reply-To: <1058476678.2171450.1637050446261@mail.yahoo.com>

I ran into this problem several months back, so I re-installed with 
brtfs. No issues at all, and never looked back!

On 16/11/2021 08:14, Jaft via wrote:
>   Oh, that's really cool. Good to know; I've never used anything outside of (ex)fat, ntfs, or ext4 and btrfs sounds interesting. I may have to play around with it more extensively, at some point.
> Jonathan
>      On Sunday, November 14, 2021, 09:18:22 PM CST, Thiago Jung Bauermann <bauermann@kolabnow.com> wrote:
>   
>   Hello Jonathan,
>
> Em domingo, 14 de novembro de 2021, às 15:47:54 -03, Jaft via escreveu:
>> Out of curiosity, I read that Btrfs requires periodic
>> fragmentation; how often do you find yourself doing it and do you use
>> any particular program for it (if you don't mind sharing, of course; I
>> know it's not directly Guix related)?
> I use btrfs for several years now — not with Guix System, though I do have
> Guix installed on top of Ubuntu on btrfs so I do have /gnu/store on btrfs.
> My experience is that it is zero-maintenance, at least on a personal laptop
> workload.
>
> Btrfs has matured a lot over the years, so there’s a fair amount of
> outdated advice still floating around on the Internet. You’re probably
> thinking of the ‘btrfs balance’ command. In the past, it was useful to run
> it every once in a while to avoid spurious ENOSPC errors. This problem has
> since been fixed, and current advice is that regular use of “btrfs balance”
> is now considered detrimental rather than beneficial since it puts more
> load/stress on the disk without any practical benefit.
>


      reply	other threads:[~2021-11-19 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <833262586.1528194.1636888480202.ref@mail.yahoo.com>
2021-11-14 11:14 ` Running Out of Inodes Jaft via
2021-11-14 13:47   ` phodina via
2021-11-14 18:47     ` Jaft via
2021-11-14 21:01       ` Vincent Legoll
2021-11-15  6:46         ` Dr. Arne Babenhauserheide
2021-11-16  8:11         ` Jaft via
2021-11-15  3:18       ` Thiago Jung Bauermann
2021-11-16  8:14         ` Jaft via
2021-11-19 19:09           ` Paul Jewell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72502e63-f7c7-cfb9-ee1b-90b3c10ff3a7@teulu.org \
    --to=paul@teulu.org \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).