From: David Masover <ninja@slaphack.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: when will it end?
Date: Wed, 27 Oct 2004 01:13:16 -0500 [thread overview]
Message-ID: <417F3C7C.2020408@slaphack.com> (raw)
In-Reply-To: <20041027033443.GE25932@backtop.namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
| current repacker code state is 'unsupported', it is even removed from the
| latest -mm kernels. Namesys plans are to make the repacker proprietary.
Really?
I sort of thought the priority was to get into the mainstream kernel, so
this seems an odd move. Why do something that decreases your benchmark?
~ And how much would people be willing to pay you when most Unix
filesystems are rarely (if ever) repacked and Windows (even DOS, I
think) comes with a free repacker of its own?
The current state of the repacker suggests that the tradeoff is not
worth it. If it takes longer than 2 days for an initial repack of a
filesystem like mine, the total amount of time I have to spend waiting
for the system while it's dog-slow and repacking is likely more than the
time I'd save by having it be slightly faster the rest of the time, or
even the time I'd have to work at minimum wage to buy more storage to
cover space the repacker could save me.
Compare this to Norton SpeedDisk, which takes about half an hour to
defrag a 20-40 gig FAT32/NTFS drive -- the first time. After that, if
run daily, it takes 10-15 mins.
But also, is chunk_size measured in megabytes? (mine was 512) Does it
mean what I think it means?
If the repacker is still free next time I go on vacation, I'll try again
- -- see if a week or two will straighten things out.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQX88e3gHNmZLgCUhAQIXiQ//fnR727WKFmhkiP/9w02YhANuImptkokC
KjLVJ8LkaOtz7OHecVqrIWNP2V13FDpp/Tn5Nf+h9iDeem6wF9rw4kXM6QX2NNFk
AD5G3dYKLEMAPDkSAXYVqMv6ykI9CH61ELNHBDatfj3gBjz0uLB0kIStI6lM1nNq
Pem2FmqWcM+3SVYEvmFuN4/oBJjwWyNav7CAWt58tvBqY703BNQmsLwEQBrcMAo8
ifM07H0JRXT9qnKYCNKAbmUhInOAr8IUIN36OUTd/Wp35K3/1C6LicGyG6wDy51b
aT0y4eZd0hTRZVkG5PCJ3Naz1GA56BFIts8Kvi9JtBJeza4/y0xZAtycZjeVr7Hu
ufMjZVWgZTswiOFvNXAVFtJ6RnVDVELnKJtHI6EkFRuyJdgQKcz1oII2f//VORU0
IST7icAw1ZSSfF08dSnhpNCFVf4ZuSAz/V6VrgFup5+cerg23DGo3bZ+K5I49//3
hOVNC2wedl8hziNt2kKd7yDNU7WpaPR3PLOusrPsJi25YRAmIhXjDanwOt3XFA3c
jhlTNTApj25FqphP1oCV9PNlUR0xYJXVHCnz8Aiu9ED0Yir8ECyY8Wm9Zgs1haec
dPelzN5KioLnE5+0dLvDaYcMvewA7Vy8NwJ5z/KfcnSpD7dvH90wDE1KNbpkjZxt
nH5vzVbtgEU=
=oGZA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-10-27 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 0:57 when will it end? David Masover
2004-10-27 3:34 ` Alex Zarochentsev
2004-10-27 6:13 ` David Masover [this message]
2004-10-27 8:31 ` Spam
2004-10-27 16:59 ` Hans Reiser
2004-10-27 17:06 ` Spam
2004-10-28 2:09 ` David Masover
2004-10-30 16:23 ` Redeeman
2004-11-18 5:07 ` David Masover
2004-11-18 10:18 ` Christian Mayrhuber
2004-11-22 3:16 ` Thomas Graham
2004-10-27 18:52 ` Alex Zarochentsev
2004-10-28 1:49 ` David Masover
2004-10-28 8:29 ` mjt
-- strict thread matches above, loose matches on Subject: below --
2004-11-18 17:15 Andreas Sundstrom
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=417F3C7C.2020408@slaphack.com \
--to=ninja@slaphack.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@namesys.com \
/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 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.