for large files.
-Original Message-
From: Arnd Bergmann [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 31, 2004 4:38 AM
To: [EMAIL PROTECTED]
Subject: Re: Myth of the 1K blocksize on eckd - revisited
On Wednesday 31 March 2004 01:36, Jim Sibley wrote:
But, in general, I would say
Jim Sibley wrote:
- I'm sure other more skewed distributions would give
different results.
The best skewed distribution could be your own, so we may get the horse
dead by this:
Given this 4K filesystem, would I save space when I made it 1K blocks?
I think running a few find -size commands would
On Wednesday 31 March 2004 01:36, Jim Sibley wrote:
But, in general, I would say that the 4k blocksize is
preferable in the majority of cases. The space lost to
eckd overhead is probably worse than any advantages
you might get with small blocksizes.
Right. Of course one might just use
Hi Everyone,
I just put on SuSE SP3. When I IPL'd, it gives me these messages:
Loading module dasd_mod dasd=$dasd ...
insmod: dasd_mod: no module by that name found
Loading module dasd_eckd_mod ...
I just put on SuSE SP3. When I IPL'd, it gives me these messages:
Loading module dasd_mod dasd=$dasd ...
insmod: dasd_mod: no module by that name found
Loading module dasd_eckd_mod ...
insmod: dasd_eckd_mod: no module by that name found
kmod: failed to exec /sbin/modprobe -s -k
In reply to Ron:
The best skewed distribution could be your own, so we
may get the horsedead by this: Given this 4K
filesystem, would I save space when I made it 1K
blocks?
Agreed. I looked at /etc, which has a lot of small
files and the average files size was 5900 bytes - not
a goot candidate
However, I could not
recommend ext2 as a filesystem because it is too
easily damanaged (sic)
How so?
Rod
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO
Rod wrte:
However, I could not
recommend ext2 as a filesystem because it is too
easily damanaged (sic)
How so?
The Linux file systems are heavily cached and allow
dirty writes of the data - i.e., the data in memory
is not immediately synced with the hardware copy. This
is controlled by the
Sorry for pushing this into the ground, but I'm still
bothered by the it depends response for using 1K
blocks on eckd devices. In the various file systems
I've seen on various platforms, 1k blocks are only
useful for very small files with none of them very
big.
So, to quantify this, I did some
