From: Danny Milosavljevic <dannym@scratchpost.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, 33676@debbugs.gnu.org
Subject: bug#33676: GuixSD on eoma68-a20?
Date: Sat, 15 Dec 2018 20:19:04 +0100 [thread overview]
Message-ID: <20181215201904.62659d07__47418.4021856219$1544901503$gmane$org@scratchpost.org> (raw)
In-Reply-To: <20181215102906.GA4621@jurong>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
Hi Andreas,
On Sat, 15 Dec 2018 11:29:06 +0100
Andreas Enge <andreas@enge.fr> wrote:
> On Fri, Dec 14, 2018 at 09:50:26PM +0100, Danny Milosavljevic wrote:
> > can you check whether dirindex (hashtables for directory) is enabled?
> > # tune2fs -l /dev/... | grep -o dir_index
> > See also https://blog.merovius.de/2013/10/20/ext4-mysterious-no-space-left-on.html
>
> It was, and I disabled it. Hopefully this does not break anything...
> But does this not mean a big performance hit on /gnu/store/.links?
It does mean that because it uses a linear search to find the file names now.
What ext filesystem is it?
https://en.wikipedia.org/wiki/Ext4 says that ext4 supports B trees - which
should have no problems with hash collisions (it uses operator< to construct
a tree -- and not hashes to construct a list).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-15 19:20 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 16:39 GuixSD on eoma68-a20? swedebugia
2018-12-08 17:12 ` Danny Milosavljevic
2018-12-08 17:34 ` bug#33676: " Ricardo Wurmus
2018-12-08 17:34 ` Ricardo Wurmus
2018-12-08 19:15 ` Danny Milosavljevic
2018-12-08 23:30 ` Ludovic Courtès
2018-12-08 23:30 ` Ludovic Courtès
2018-12-08 20:59 ` Mark H Weaver
2018-12-08 23:53 ` bug#33676: " Danny Milosavljevic
2018-12-08 23:53 ` Danny Milosavljevic
2018-12-09 11:48 ` bug#33676: " Danny Milosavljevic
2018-12-09 11:48 ` Danny Milosavljevic
2018-12-09 21:32 ` Mark H Weaver
2018-12-11 8:13 ` bug#33676: " Efraim Flashner
2018-12-11 8:13 ` Efraim Flashner
2018-12-11 17:34 ` Ludovic Courtès
2018-12-12 8:12 ` bug#33676: " Danny Milosavljevic
2018-12-12 8:12 ` Danny Milosavljevic
2018-12-14 10:48 ` Ludovic Courtès
2018-12-15 19:21 ` bug#33676: " Danny Milosavljevic
2018-12-15 19:21 ` Danny Milosavljevic
2018-12-16 15:59 ` bug#33676: " Ludovic Courtès
2018-12-16 20:14 ` Danny Milosavljevic
2018-12-16 20:14 ` bug#33676: " Danny Milosavljevic
2018-12-14 10:48 ` Ludovic Courtès
2018-12-11 17:34 ` Ludovic Courtès
2018-12-09 21:32 ` Mark H Weaver
2018-12-08 20:59 ` Mark H Weaver
2018-12-09 21:51 ` Andreas Enge
2018-12-10 10:30 ` Danny Milosavljevic
2018-12-10 21:12 ` Andreas Enge
2018-12-14 20:50 ` Danny Milosavljevic
2018-12-15 10:29 ` Andreas Enge
2018-12-15 19:04 ` Mark H Weaver
2018-12-16 15:08 ` Andreas Enge
2018-12-16 15:08 ` Andreas Enge
2018-12-15 19:04 ` Mark H Weaver
2018-12-15 19:19 ` Danny Milosavljevic [this message]
2018-12-15 19:19 ` Danny Milosavljevic
2018-12-15 10:29 ` Andreas Enge
2018-12-14 20:50 ` Danny Milosavljevic
2018-12-21 23:09 ` Danny Milosavljevic
2018-12-22 8:33 ` swedebugia
2018-12-22 8:33 ` swedebugia
2018-12-22 8:44 ` Danny Milosavljevic
2018-12-23 5:09 ` swedebugia
2018-12-23 8:54 ` swedebugia
2018-12-23 8:54 ` swedebugia
2018-12-23 5:09 ` swedebugia
2018-12-22 8:44 ` Danny Milosavljevic
2018-12-22 8:47 ` swedebugia
2018-12-22 9:11 ` Danny Milosavljevic
2018-12-22 9:11 ` Danny Milosavljevic
2018-12-22 8:47 ` swedebugia
2018-12-10 21:12 ` Andreas Enge
2018-12-14 11:09 ` ENOSPC upon offloading Ludovic Courtès
2018-12-14 11:09 ` bug#33676: " Ludovic Courtès
2018-12-09 21:51 ` bug#33676: GuixSD on eoma68-a20? Andreas Enge
2018-12-11 2:04 ` Luke Kenneth Casson Leighton
2018-12-21 23:05 ` Danny Milosavljevic
2018-12-21 23:49 ` Luke Kenneth Casson Leighton
2020-04-07 13:45 ` Marius Bakke
2020-04-07 15:17 ` Ricardo Wurmus
2020-04-07 15:33 ` Marius Bakke
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='20181215201904.62659d07__47418.4021856219$1544901503$gmane$org@scratchpost.org' \
--to=dannym@scratchpost.org \
--cc=33676@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.