-----BEGIN PGP SIGNED MESSAGE----- On Sun, 30 Jan 2000, Colin Watson wrote:
> >I suspect this problem has something to do with 'sparse files'. > > Right idea, though not the usual terminology so documentation searches > might have failed you (that reminded me of sparse superblocks or perhaps > files containing "holes", both of which are entirely different; that's > probably just me free-associating again, though). <snip> No, you were right. I was referring to files with "holes", though after reading your reply and giving it some further thought, it's pretty obvious that none of the operations I performed would have created sparse files. > The block size on your > new /usr is larger than that on your old /usr, that's all. Use > '/sbin/tune2fs -l /dev/sda10' and '/sbin/tune2fs -l /dev/sda11' to see > the various parameters of the two filesystems. (Make sure to unmount the > filesystem or remount it read-only before changing any filesystem > parameters with tune2fs, though.) Exactly right. Thanks a whole lot for such a quick reply! Ooh, this is bringing back fond memories of my operating systems classes in school. One of them focused almost entirely on filesystems, so this blocksize issue and the space/speed issue that comes with different size blocks are somewhat familiar to me. Interesting... noah PGP Public Key available at http://www.morgul.net/~frodo/mail.html or by `finger -l [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: 2.6.3a Charset: noconv iQCVAwUBOJOrIIdCcpBjGWoFAQHG0AP/ZETpSbZNfEaSvkbd62lonFWgmE5iwxtJ rcKWUyjCRdW12BrrpZFEVGsgbrdj/NRuqIJtv8S3P7dOjVktMHcQXB3uYay8gYuz NItFmohLSAOyLTKVsqcfPIGWvQh3AazkDcxHD3ip/WEQaNWOh36RQljZNLWPJYTm r6u//QF7T54= =LiKd -----END PGP SIGNATURE-----
