Hi Edgar,
Edgar =?iso-8859-1?B?RnXf?= wrote:
> In any case, for all practical reasons, my question in answered because
> the Borg repository holds mostly large files, which I learned are never
> fragmented.
I have a many years old borg repository that now has 11,080 files. Of
these, 2,626 are
Date:Wed, 30 Apr 2025 09:27:45 +0200
From:Edgar Fu�
Message-ID:
| > By "fragments in use" do you mean
| >
| > 1) Fragment-sized pieces of disk with file data in them?
| > 2) Blocks with some but not all fragments occupied?
| > 3) Files with trailing sub-bl
Date:Wed, 30 Apr 2025 09:42:31 +0200
From:Edgar Fu�
Message-ID:
| > Note that the numbers in parentheses [of the fsck output] are what is free
| Oops. I never understood it that way.
Take Greg's filesystem:
603427 files, 48107560 used, 11047434 free (1845
> The indirect blocks, and all blocks reached via an indirect block,
> are all full blocks, never a fragment.
Oops, I didn't know that. That's very helpful.
> And fragments are only ever right at the end of a small file
That I /did/ know.
> Note that the numbers in parentheses [of the fsck outpu
> Depends on exactly what you want, though for most likely "what you
> want"s, the answer is "no". (But see below.)
>
> By "fragments in use" do you mean
>
> 1) Fragment-sized pieces of disk with file data in them?
> 2) Blocks with some but not all fragments occupied?
> 3) Files with trailing su
>>> On a populated FFS, is there an easy way to determine how many
>>> fragments are in use or how many blocks are split into fragments?
Depends on exactly what you want, though for most likely "what you
want"s, the answer is "no". (But see below.)
By "fragments in use" do you mean
1) Fragment-
Date:Tue, 29 Apr 2025 12:01:05 -0400
From:Greg Troxel
Message-ID:
| Edgar Fu� writes:
|
| > On a populated FFS, is there an easy way to determine how many
| > fragments are in use or how many blocks are split into fragments?
|
| dumpfs might help.
Not a
Edgar Fuß writes:
> On a populated FFS, is there an easy way to determine how many
> fragments are in use or how many blocks are split into fragments?
dumpfs might help.My impression is that files are always the highest
number of blocks that fit, and then fragments as needed.If the files
Just in case: What this really is about is chosing the RAID stripe unit size.
On a three-component RAID 5, I think I basically have two options: make a
stripe the size of a fragment or make it the size of a block.
The data on the RAID set is a Borg backup, and I can examine data on another
backup
On Mon, Jun 06, 2011 at 05:11:51PM -0500, Eric Haszlakiewicz wrote:
> On Mon, Jun 06, 2011 at 10:38:07AM -0700, Brian Buhrow wrote:
> > Hello. I like this explanation. Can you help clarify by giving a
> > theoretical example?
> > -thanks
> > -Brian
>
> If sectPerSU is the per-component strip
op-posting.
Q: What is the most annoying thing on usenet and in e-mail?
> On Jun 6, 9:50am, Thor Lancelot Simon wrote:
> } Subject: Re: RAID stripe size (was: 5.1 RAID5 write performance)
> } On Mon, Jun 06, 2011 at 03:24:15PM +0200, Edgar Fu?
Hello. I like this explanation. Can you help clarify by giving a
theoretical example?
-thanks
-Brian
On Jun 6, 9:50am, Thor Lancelot Simon wrote:
} Subject: Re: RAID stripe size (was: 5.1 RAID5 write performance)
} On Mon, Jun 06, 2011 at 03:24:15PM +0200, Edgar Fu? wrote:
} > > A
> So, what's the advantage of a larger sectPerSU?
Larger is not necessarily better. Larger than the typical write size
(which is usually the filesystem block or frag size) is actually a
*dis*advantage, because it means that common writes force RMW cycles.
Much smaller than the typical access siz
> The filesystem block size (or, where this is not possible, the maximum
> cluster size the filesystem will write) should be equal to sectPerSU
> times the number of data (not parity) disks.
Yes. That's what I would call ``stripe size''. Is that the wrong term?
I have sectPerSU=32, so with a three
On Mon, Jun 06, 2011 at 03:24:15PM +0200, Edgar Fu? wrote:
> > Ah, yes, the old
> > rmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmw
> > cycle. Gets me every time.
> OK, I've fixed that (before doing the tests I reported the last two days).
>
> So
> Ah, yes, the old
> rmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmwrmw
> cycle. Gets me every time.
OK, I've fixed that (before doing the tests I reported the last two days).
So, what's the advantage of a larger sectPerSU?
It appears to me that the
16 matches
Mail list logo
