I notice when the system fsck's then it has a % of non-contiguous blocks after it has completed and I am wondering if this is signaling bad block possibility or a failing drive or just blocks that had to be rearranged? -- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================
On Sunday 25 Jul 2004 12:01 pm, Hylton Conacher (ZR1HPC) wrote:
I notice when the system fsck's then it has a % of non-contiguous blocks after it has completed and I am wondering if this is signaling bad block possibility or a failing drive or just blocks that had to be rearranged?
AIUI this is approximately equivalent to file fragmentation, but there is nowhere near the same effect on performance with *nix filesystems as there is with FAT based systems. In the vast majority of cases they are absolutely nothing to concern yourself with. HTH Dylan -- "I see your Schwartz is as big as mine" -Dark Helmet
On Sunday 25 July 2004 04:42 am, Dylan wrote:
On Sunday 25 Jul 2004 12:01 pm, Hylton Conacher (ZR1HPC) wrote:
I notice when the system fsck's then it has a % of non-contiguous blocks after it has completed and I am wondering if this is signaling bad block possibility or a failing drive or just blocks that had to be rearranged?
AIUI this is approximately equivalent to file fragmentation, but there is nowhere near the same effect on performance with *nix filesystems as there is with FAT based systems. In the vast majority of cases they are absolutely nothing to concern yourself with.
HTH Dylan
And you will see that the message tells you that about 1% or something like that are non-contiguous, which is trivial. -- Tony Alfrey tonyalfrey@earthlink.net "I'd Rather Be Sailing"
participants (3)
-
Dylan
-
Hylton Conacher (ZR1HPC)
-
Tony Alfrey