From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New distfile mirror layout
Date: Fri, 18 Oct 2019 22:49:21 +0200 [thread overview]
Message-ID: <02507080f1e18d0382f551239819fb784cb0c05d.camel@gentoo.org> (raw)
In-Reply-To: <A11BCBC8-26C4-4F7A-A608-228B6717C329@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On Fri, 2019-10-18 at 15:53 -0400, Richard Yao wrote:
> > On Oct 18, 2019, at 9:42 AM, Michał Górny <mgorny@gentoo.org> wrote:
> >
> > Hi, everybody.
> >
> > It is my pleasure to announce that yesterday (EU) evening we've switched
> > to a new distfile mirror layout. Users will be switching to the new
> > layout either as they upgrade Portage to 2.3.77 or -- if they upgraded
> > already -- as their caches expire (24hrs).
> >
> > The new layout is mostly a bow towards mirror admins, for some of whom
> > having a 60000+ files in a single directory have been a problem.
> > However, I suppose some of you also found e.g. the directory index
> > hardly usable due to its size.
> This sounds like a filesystem issue. Do we know which filesystems are suffering?
>
> ZFS should be fine. I believe ext2/ext3 have problems with this many files. ext4 is probably okay, but don’t quote me on that.
Ext2, VFAT and NTFS were mentioned on the bug [1], though I suppose this
may apply only to older ntfs versions. NFS has been mentioned too.
However, just because modern filesystems can handle them efficiently, it
doesn't mean having directories that huge comes with zero cost.
[1] https://bugs.gentoo.org/534528
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-10-18 20:49 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 13:41 [gentoo-dev] New distfile mirror layout Michał Górny
2019-10-18 19:53 ` Richard Yao
2019-10-18 20:49 ` Michał Górny [this message]
2019-10-19 1:09 ` Richard Yao
2019-10-19 6:17 ` Michał Górny
2019-10-19 8:20 ` Richard Yao
2019-10-19 19:26 ` Richard Yao
2019-10-19 20:02 ` Michał Górny
2019-10-19 22:48 ` Richard Yao
2019-10-22 0:46 ` James Cloos
2019-10-19 13:31 ` Fabian Groffen
2019-10-19 13:53 ` Michał Górny
2019-10-19 23:24 ` Joshua Kinard
2019-10-19 23:57 ` Alec Warner
2019-10-20 0:14 ` Joshua Kinard
2019-10-20 6:51 ` Michał Górny
2019-10-20 8:25 ` Joshua Kinard
2019-10-20 8:32 ` Michał Górny
2019-10-20 9:21 ` Joshua Kinard
2019-10-20 9:44 ` Michał Górny
2019-10-20 20:57 ` Joshua Kinard
2019-10-21 0:05 ` Joshua Kinard
2019-10-21 5:51 ` Ulrich Mueller
2019-10-21 10:17 ` Kent Fredric
2019-10-21 21:34 ` Mikle Kolyada
2019-10-21 10:13 ` Kent Fredric
2019-10-23 5:16 ` Joshua Kinard
2019-10-29 16:35 ` Kent Fredric
2019-10-20 17:09 ` Matt Turner
2019-10-21 16:42 ` Richard Yao
2019-10-21 23:36 ` Matt Turner
2019-10-23 5:18 ` Joshua Kinard
2019-10-23 17:06 ` William Hubbs
2019-10-23 18:38 ` William Hubbs
2019-10-23 22:04 ` William Hubbs
2019-10-24 4:30 ` Michał Górny
2019-10-22 6:51 ` Jaco Kroon
2019-10-22 8:43 ` Ulrich Mueller
2019-10-22 8:46 ` Jaco Kroon
2019-10-23 23:47 ` ext4 readdir performance - was " Richard Yao
2019-10-24 0:01 ` Richard Yao
2019-10-23 1:21 ` Rich Freeman
2019-10-28 23:24 ` Chí-Thanh Christopher Nguyễn
2019-10-29 4:27 ` Michał Górny
2019-10-29 9:34 ` Fabian Groffen
2019-10-29 11:11 ` Michał Górny
2019-10-29 12:23 ` Ulrich Mueller
2019-10-29 12:43 ` Michał Górny
2019-10-29 13:03 ` Ulrich Mueller
2019-10-29 13:09 ` Ulrich Mueller
2019-10-29 13:52 ` Michał Górny
2019-10-29 14:17 ` Ulrich Mueller
2019-10-29 14:33 ` Fabian Groffen
2019-10-29 14:45 ` Michał Górny
2019-10-29 14:56 ` Fabian Groffen
2019-10-29 13:51 ` Michał Górny
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=02507080f1e18d0382f551239819fb784cb0c05d.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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