-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been investigating why parted's rescue operation is so slow and it seems that it is largely due to AFFS, so I am trying to understand it a bit. I notice that it appears to read the first 16 sectors of the disk ( not the partition or potential partition ) looking for some sort of "rigid disk" block. Why is this? Wouldn't this prevent the possibility of having such a filesystem on a gpt partitioned disk, or a disk with grub installed? Or a loop image? I checked the kernel affs code and it has a different way of computing the fs block size ( which seems to be the reason for reading the rigid disk block ).
Another reason for the slowness is that affs registers 15 different variants and each one must be probed separately resulting in 15 times the number of reads. Is it really necessary to differentiate between all of these sub types in the output of parted print? Also where can I find tools for creating such a filesystem for testing purposes? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJUtDFJAAoJENRVrw2cjl5RH0YIAKbAQp9NXWbmIUH9pmSS+q67 h49XTWS1YKkT6PLThHBVMpNTEjQSGUvk5IJEVIBl6Bmmk4bTr+wgDesHv0l+5rFI RX4NG+vB3P+uyL5//w+Lbtc4q3cd4wtKAeowBIaLJbRK5z+MB+cufkR1UJLrhpGB ywMZAyoOZY4kFsFgeFSyFdXoQiJ4xGZ7Pq0u17jQtv8E4dUrbSEEUpTPAdur1g6B W0hY/5wT/n7OU/zwveejfpaQP9ocGvoyIU4nnXfHvixXKfwCC8y4OzNjZD6fcbiE 8SqrXsPbzmtAFxoN9chdlpaBZ21/EyzEYqjrbUFC7a2sG4E/VV3I0a5RWuBvevk= =I6RE -----END PGP SIGNATURE-----
