From: "raymond jennings" <highwind747@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: FW: [ERR] [IDEA] - run-length compaction of block numbers
Date: Thu, 29 Jan 2004 10:37:06 -0800 [thread overview]
Message-ID: <BAY1-F96zCI50hUlhuv000153ab@hotmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
>From: postmaster@kornet.net
>To: highwind747@hotmail.com
>Subject: [ERR] [IDEA] - run-length compaction of block numbers
>Date: Wed, 21 Jan 2004 20:03:17 +0900
>
>Transmit Report:
>
> To: pupuru@kornet.net, 452 Requested action not taken: insufficient
>system storage.[28,-1,41]
_________________________________________________________________
Check out the new MSN 9 Dial-up fast & reliable Internet access with prime
features! http://join.msn.com/?pgmarket=en-us&page=dialup/home&ST=1
[-- Attachment #2: Type: message/rfc822, Size: 2628 bytes --]
From: "raymond jennings" <highwind747@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: [IDEA] - run-length compaction of block numbers
Date: Fri, 16 Jan 2004 11:38:59 -0800
Message-ID: <1074682997179055492.1.ppp5@ppp5>
Is there any value in creating a new filesystem that encodes long contiguous
blocks as a single block run instead of multiple block numbers? A long file
may use only a few block runs instead of many block numbers if there is
little fragmentation (usually the case). Also dynamic allocation of
inodes...etc. The details are long; anyone interested can e-mail me
privately.
_________________________________________________________________
Rethink your business approach for the new year with the helpful tips here.
http://special.msn.com/bcentral/prep04.armx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2004-01-29 18:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BAY1-F96zCI50hUlhuv000153ab@hotmail.com \
--to=highwind747@hotmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®