----------------------------------------------------------------------------------
@MSGID: 3:633/10 ea4f8427
@REPLY: 3:633/10 2d85de81
@PID: PyGate 1.5.19
@TID: PyGate/Linux 1.5.19
@NEWSREADER: Microsoft Outlook Express 6.00.2900.5512
@CHRS: ASCII 1
@TZUTC: 0100
@REPLYADDR: address@is.invalid
@REPLYTO: 3:633/10 UUCP
@RFC-Message-ID: <11drne9$3ufa6$1@dont-email.me>
Richard,
> The drive doesn`t know which (logical) blocks are not part of
> a file, unless the OS tells it.
Inxdeed. I mixed up the drive smarts with the filesystem the OS puts on the
drive.
iow, the drive has no concept of used and non-used blocks. It just goes for
the (write)usage-count of each block on its drive. Contents are irrelevant.
It could swap two blocks that are both in use by a partition and the
filesystem on it.
The /only/ reason I could imagine for having blocks in their erased state
(not sure if that is all zeroes or all ones) is that, when swapping such a
block in, the erase cycle could be skipped - making it a bit faster.
Regards,
Rudy Wieser
--- PyGate Linux v1.5.19
* Origin: Dragon`s Lair, PyGate NNTP<>Fido Gate (3:633/10)
SEEN-BY: 19/10 50/109 153/757 218/840 840 220/70 221/1 6 360 226/17 100
SEEN-BY: 229/426 240/1120 267/800 301/1 113 812 310/31 335/364 341/66 463/68
SEEN-BY: 550/278 633/10 280 281 416 418 420 422 509 2744 712/848 1321 770/1 3
SEEN-BY: 770/100 340 772/210 220 230 5001/100 5005/49 5020/715 848 1042 4441
SEEN-BY: 5020/12000 5023/24 5030/49 722 1081 1474 5051/44 5061/133 5075/128
@PATH: 633/10 280 770/1 218/840 221/6 301/1 5020/1042 4441 715