diff for duplicates of <4C5D0BC2.1040706@linux.vnet.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 4aedca0..f57a736 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -2,39 +2,30 @@ On 08/06/2010 02:03 PM, Christoph Hellwig wrote: > Something is deeply wrong here. Raw block device access has a 1:1 -> mapping between logical and physical block numbers. They really shou= -ld +> mapping between logical and physical block numbers. They really should > never be non-contiguous. At least I did nothing I know about to break it :-) -As I mentioned just iozone using direct I/O (-I flag of iozone then=20 +As I mentioned just iozone using direct I/O (-I flag of iozone then using O_DIRECT for the file) on a ext2 file-system. -The file system was coming clean out of mkfs the file was written with=20 +The file system was coming clean out of mkfs the file was written with iozone one step before the traced read run. -The only uncommon thing here might be the block device, which is a scsi= -=20 -disk on our SAN servers (I'm running on s390) - so the driver in charge= -=20 +The only uncommon thing here might be the block device, which is a scsi +disk on our SAN servers (I'm running on s390) - so the driver in charge is zfcp (drivers/s390/scsi/). -I could use dasd (drivers/s390/block) disks as well, but I have no=20 -blktrace of them yet - what I already know is that they show a similar=20 -cost increase. On monday I should be able to get machine resources to=20 +I could use dasd (drivers/s390/block) disks as well, but I have no +blktrace of them yet - what I already know is that they show a similar +cost increase. On monday I should be able to get machine resources to verify that both disk types are affected. -Let me know if I can do anything else on my system to shed some light o= -n=20 +Let me know if I can do anything else on my system to shed some light on the matter. ---=20 +-- -Gr=FCsse / regards, Christian Ehrhardt +Grüsse / regards, Christian Ehrhardt IBM Linux Technology Center, System z Linux Performance --- -To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= -" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 6a880f8..7d6fcfa 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -15,41 +15,32 @@ "\n" "On 08/06/2010 02:03 PM, Christoph Hellwig wrote:\n" "> Something is deeply wrong here. Raw block device access has a 1:1\n" - "> mapping between logical and physical block numbers. They really shou=\n" - "ld\n" + "> mapping between logical and physical block numbers. They really should\n" "> never be non-contiguous.\n" "\n" "At least I did nothing I know about to break it :-)\n" "\n" - "As I mentioned just iozone using direct I/O (-I flag of iozone then=20\n" + "As I mentioned just iozone using direct I/O (-I flag of iozone then \n" "using O_DIRECT for the file) on a ext2 file-system.\n" - "The file system was coming clean out of mkfs the file was written with=20\n" + "The file system was coming clean out of mkfs the file was written with \n" "iozone one step before the traced read run.\n" "\n" - "The only uncommon thing here might be the block device, which is a scsi=\n" - "=20\n" - "disk on our SAN servers (I'm running on s390) - so the driver in charge=\n" - "=20\n" + "The only uncommon thing here might be the block device, which is a scsi \n" + "disk on our SAN servers (I'm running on s390) - so the driver in charge \n" "is zfcp (drivers/s390/scsi/).\n" - "I could use dasd (drivers/s390/block) disks as well, but I have no=20\n" - "blktrace of them yet - what I already know is that they show a similar=20\n" - "cost increase. On monday I should be able to get machine resources to=20\n" + "I could use dasd (drivers/s390/block) disks as well, but I have no \n" + "blktrace of them yet - what I already know is that they show a similar \n" + "cost increase. On monday I should be able to get machine resources to \n" "verify that both disk types are affected.\n" "\n" - "Let me know if I can do anything else on my system to shed some light o=\n" - "n=20\n" + "Let me know if I can do anything else on my system to shed some light on \n" "the matter.\n" "\n" "\n" "\n" - "--=20\n" + "-- \n" "\n" - "Gr=FCsse / regards, Christian Ehrhardt\n" - "IBM Linux Technology Center, System z Linux Performance\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-fsdevel=\n" - "\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + "Gr\303\274sse / regards, Christian Ehrhardt\n" + IBM Linux Technology Center, System z Linux Performance -a6fb718405a6461c187dcd64f738f3c2f0bf255954d888808b72a6c91a069b6a +00c16841b71304f96a5ca5aba8a76386266b6dffdd71a2b1338389b3a463d796
diff --git a/a/1.txt b/N2/1.txt index 4aedca0..78b2d88 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -2,39 +2,34 @@ On 08/06/2010 02:03 PM, Christoph Hellwig wrote: > Something is deeply wrong here. Raw block device access has a 1:1 -> mapping between logical and physical block numbers. They really shou= -ld +> mapping between logical and physical block numbers. They really should > never be non-contiguous. At least I did nothing I know about to break it :-) -As I mentioned just iozone using direct I/O (-I flag of iozone then=20 +As I mentioned just iozone using direct I/O (-I flag of iozone then using O_DIRECT for the file) on a ext2 file-system. -The file system was coming clean out of mkfs the file was written with=20 +The file system was coming clean out of mkfs the file was written with iozone one step before the traced read run. -The only uncommon thing here might be the block device, which is a scsi= -=20 -disk on our SAN servers (I'm running on s390) - so the driver in charge= -=20 +The only uncommon thing here might be the block device, which is a scsi +disk on our SAN servers (I'm running on s390) - so the driver in charge is zfcp (drivers/s390/scsi/). -I could use dasd (drivers/s390/block) disks as well, but I have no=20 -blktrace of them yet - what I already know is that they show a similar=20 -cost increase. On monday I should be able to get machine resources to=20 +I could use dasd (drivers/s390/block) disks as well, but I have no +blktrace of them yet - what I already know is that they show a similar +cost increase. On monday I should be able to get machine resources to verify that both disk types are affected. -Let me know if I can do anything else on my system to shed some light o= -n=20 +Let me know if I can do anything else on my system to shed some light on the matter. ---=20 +-- -Gr=FCsse / regards, Christian Ehrhardt +Grüsse / regards, Christian Ehrhardt IBM Linux Technology Center, System z Linux Performance -- -To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= -" in +To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index 6a880f8..a91f84d 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -15,41 +15,36 @@ "\n" "On 08/06/2010 02:03 PM, Christoph Hellwig wrote:\n" "> Something is deeply wrong here. Raw block device access has a 1:1\n" - "> mapping between logical and physical block numbers. They really shou=\n" - "ld\n" + "> mapping between logical and physical block numbers. They really should\n" "> never be non-contiguous.\n" "\n" "At least I did nothing I know about to break it :-)\n" "\n" - "As I mentioned just iozone using direct I/O (-I flag of iozone then=20\n" + "As I mentioned just iozone using direct I/O (-I flag of iozone then \n" "using O_DIRECT for the file) on a ext2 file-system.\n" - "The file system was coming clean out of mkfs the file was written with=20\n" + "The file system was coming clean out of mkfs the file was written with \n" "iozone one step before the traced read run.\n" "\n" - "The only uncommon thing here might be the block device, which is a scsi=\n" - "=20\n" - "disk on our SAN servers (I'm running on s390) - so the driver in charge=\n" - "=20\n" + "The only uncommon thing here might be the block device, which is a scsi \n" + "disk on our SAN servers (I'm running on s390) - so the driver in charge \n" "is zfcp (drivers/s390/scsi/).\n" - "I could use dasd (drivers/s390/block) disks as well, but I have no=20\n" - "blktrace of them yet - what I already know is that they show a similar=20\n" - "cost increase. On monday I should be able to get machine resources to=20\n" + "I could use dasd (drivers/s390/block) disks as well, but I have no \n" + "blktrace of them yet - what I already know is that they show a similar \n" + "cost increase. On monday I should be able to get machine resources to \n" "verify that both disk types are affected.\n" "\n" - "Let me know if I can do anything else on my system to shed some light o=\n" - "n=20\n" + "Let me know if I can do anything else on my system to shed some light on \n" "the matter.\n" "\n" "\n" "\n" - "--=20\n" + "-- \n" "\n" - "Gr=FCsse / regards, Christian Ehrhardt\n" + "Gr\303\274sse / regards, Christian Ehrhardt\n" "IBM Linux Technology Center, System z Linux Performance\n" "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-fsdevel=\n" - "\" in\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-fsdevel\" in\n" "the body of a message to majordomo@vger.kernel.org\n" More majordomo info at http://vger.kernel.org/majordomo-info.html -a6fb718405a6461c187dcd64f738f3c2f0bf255954d888808b72a6c91a069b6a +aef936f14719a128f5c0a3a8d11934bc4ca26961cb6e78068c3db8d8fe8e31f4
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.