diff for duplicates of <1291810586-sup-8211@think> diff --git a/a/1.txt b/N1/1.txt index 79f62f3..d5c78c0 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,46 +1,61 @@ Excerpts from Jon Nelson's message of 2010-12-07 22:29:26 -0500: -> On Tue, Dec 7, 2010 at 3:02 PM, Chris Mason <chris.mason@oracle.com> wrote: +> On Tue, Dec 7, 2010 at 3:02 PM, Chris Mason <chris.mason@oracle.com> = +wrote: > > Excerpts from Jon Nelson's message of 2010-12-07 15:48:58 -0500: -> >> On Tue, Dec 7, 2010 at 2:41 PM, Chris Mason <chris.mason@oracle.com> wrote: +> >> On Tue, Dec 7, 2010 at 2:41 PM, Chris Mason <chris.mason@oracle.co= +m> wrote: > >> > Excerpts from Jon Nelson's message of 2010-12-07 15:25:47 -0500: -> >> >> On Tue, Dec 7, 2010 at 2:02 PM, Chris Mason <chris.mason@oracle.com> wrote: -> >> >> > Excerpts from Jon Nelson's message of 2010-12-07 14:34:40 -0500: -> >> >> >> On Tue, Dec 7, 2010 at 12:52 PM, Chris Mason <chris.mason@oracle.com> wrote: -> >> >> >> >> postgresql errors. Typically, header corruption but from the limited -> >> >> >> >> visibility I've had into this via strace, what I see is zeroed pages +> >> >> On Tue, Dec 7, 2010 at 2:02 PM, Chris Mason <chris.mason@oracle= +=2Ecom> wrote: +> >> >> > Excerpts from Jon Nelson's message of 2010-12-07 14:34:40 -05= +00: +> >> >> >> On Tue, Dec 7, 2010 at 12:52 PM, Chris Mason <chris.mason@or= +acle.com> wrote: +> >> >> >> >> postgresql errors. Typically, header corruption but from = +the limited +> >> >> >> >> visibility I've had into this via strace, what I see is z= +eroed pages > >> >> >> >> where there shouldn't be. > >> >> >> > -> >> >> >> > This sounds a lot like a bug higher up than dm-crypt. Â Zeros tend to -> >> >> >> > come from some piece of code explicitly filling a page with zeros, and -> >> >> >> > that often happens in the corner cases for O_DIRECT and a few other +> >> >> >> > This sounds a lot like a bug higher up than dm-crypt. =C2=A0= +Zeros tend to +> >> >> >> > come from some piece of code explicitly filling a page wit= +h zeros, and +> >> >> >> > that often happens in the corner cases for O_DIRECT and a = +few other > >> >> >> > places in the filesystem. > >> >> >> > -> >> >> >> > Have you tried triggering this with a regular block device? +> >> >> >> > Have you tried triggering this with a regular block device= +? > >> >> >> -> >> >> >> I just tried the whole set of tests, but with /dev/sdb directly (as +> >> >> >> I just tried the whole set of tests, but with /dev/sdb direc= +tly (as > >> >> >> ext4) without any crypt-y bits. -> >> >> >> It takes more iterations but out of 6 tests I had one failure: same +> >> >> >> It takes more iterations but out of 6 tests I had one failur= +e: same > >> >> >> type of thing, 'invalid page header in block ....'. > >> >> >> -> >> >> >> I can't guarantee that it is a full-page of zeroes, just what I saw +> >> >> >> I can't guarantee that it is a full-page of zeroes, just wha= +t I saw > >> >> >> from the (limited) stracing I did. > >> >> > > >> >> > Fantastic. Now for our usual suspects: -> +>=20 > Maybe not so fantastic. I kept testing and had no more failures. At > all. After 40+ iterations I gave up. > I went back to trying ext4 on a LUKS volume. The 'hit' ratio went to > something like 1 in 3, or better. -> +>=20 > I will continue to do testing with and without LUKS. I did /not/ > reboot between tests, but I do start with a fresh postgres database. -> +>=20 Once we trigger once without dm-crypt, dm-crypt is off the hook. Just to verify, when you say without luks, you mean without any crypto bits in use at all on the filesystems postgres uses? -Usually the trick to reproducing filesystem corruptions is adding memory +Usually the trick to reproducing filesystem corruptions is adding memor= +y pressure. The corruption is probably a bad interaction between reads and writes, and we need to make sure the reads actually happen. @@ -55,6 +70,7 @@ The idea is to trigger constant reads without having to swap heavily. -chris -- -To unsubscribe from this list: send the line "unsubscribe linux-ext4" in +To unsubscribe from this list: send the line "unsubscribe linux-ext4" i= +n 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 200a176..53f71d9 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -35,48 +35,63 @@ "\00:1\0" "b\0" "Excerpts from Jon Nelson's message of 2010-12-07 22:29:26 -0500:\n" - "> On Tue, Dec 7, 2010 at 3:02 PM, Chris Mason <chris.mason@oracle.com> wrote:\n" + "> On Tue, Dec 7, 2010 at 3:02 PM, Chris Mason <chris.mason@oracle.com> =\n" + "wrote:\n" "> > Excerpts from Jon Nelson's message of 2010-12-07 15:48:58 -0500:\n" - "> >> On Tue, Dec 7, 2010 at 2:41 PM, Chris Mason <chris.mason@oracle.com> wrote:\n" + "> >> On Tue, Dec 7, 2010 at 2:41 PM, Chris Mason <chris.mason@oracle.co=\n" + "m> wrote:\n" "> >> > Excerpts from Jon Nelson's message of 2010-12-07 15:25:47 -0500:\n" - "> >> >> On Tue, Dec 7, 2010 at 2:02 PM, Chris Mason <chris.mason@oracle.com> wrote:\n" - "> >> >> > Excerpts from Jon Nelson's message of 2010-12-07 14:34:40 -0500:\n" - "> >> >> >> On Tue, Dec 7, 2010 at 12:52 PM, Chris Mason <chris.mason@oracle.com> wrote:\n" - "> >> >> >> >> postgresql errors. Typically, header corruption but from the limited\n" - "> >> >> >> >> visibility I've had into this via strace, what I see is zeroed pages\n" + "> >> >> On Tue, Dec 7, 2010 at 2:02 PM, Chris Mason <chris.mason@oracle=\n" + "=2Ecom> wrote:\n" + "> >> >> > Excerpts from Jon Nelson's message of 2010-12-07 14:34:40 -05=\n" + "00:\n" + "> >> >> >> On Tue, Dec 7, 2010 at 12:52 PM, Chris Mason <chris.mason@or=\n" + "acle.com> wrote:\n" + "> >> >> >> >> postgresql errors. Typically, header corruption but from =\n" + "the limited\n" + "> >> >> >> >> visibility I've had into this via strace, what I see is z=\n" + "eroed pages\n" "> >> >> >> >> where there shouldn't be.\n" "> >> >> >> >\n" - "> >> >> >> > This sounds a lot like a bug higher up than dm-crypt. \303\202\302\240Zeros tend to\n" - "> >> >> >> > come from some piece of code explicitly filling a page with zeros, and\n" - "> >> >> >> > that often happens in the corner cases for O_DIRECT and a few other\n" + "> >> >> >> > This sounds a lot like a bug higher up than dm-crypt. =C2=A0=\n" + "Zeros tend to\n" + "> >> >> >> > come from some piece of code explicitly filling a page wit=\n" + "h zeros, and\n" + "> >> >> >> > that often happens in the corner cases for O_DIRECT and a =\n" + "few other\n" "> >> >> >> > places in the filesystem.\n" "> >> >> >> >\n" - "> >> >> >> > Have you tried triggering this with a regular block device?\n" + "> >> >> >> > Have you tried triggering this with a regular block device=\n" + "?\n" "> >> >> >>\n" - "> >> >> >> I just tried the whole set of tests, but with /dev/sdb directly (as\n" + "> >> >> >> I just tried the whole set of tests, but with /dev/sdb direc=\n" + "tly (as\n" "> >> >> >> ext4) without any crypt-y bits.\n" - "> >> >> >> It takes more iterations but out of 6 tests I had one failure: same\n" + "> >> >> >> It takes more iterations but out of 6 tests I had one failur=\n" + "e: same\n" "> >> >> >> type of thing, 'invalid page header in block ....'.\n" "> >> >> >>\n" - "> >> >> >> I can't guarantee that it is a full-page of zeroes, just what I saw\n" + "> >> >> >> I can't guarantee that it is a full-page of zeroes, just wha=\n" + "t I saw\n" "> >> >> >> from the (limited) stracing I did.\n" "> >> >> >\n" "> >> >> > Fantastic. Now for our usual suspects:\n" - "> \n" + ">=20\n" "> Maybe not so fantastic. I kept testing and had no more failures. At\n" "> all. After 40+ iterations I gave up.\n" "> I went back to trying ext4 on a LUKS volume. The 'hit' ratio went to\n" "> something like 1 in 3, or better.\n" - "> \n" + ">=20\n" "> I will continue to do testing with and without LUKS. I did /not/\n" "> reboot between tests, but I do start with a fresh postgres database.\n" - "> \n" + ">=20\n" "\n" "Once we trigger once without dm-crypt, dm-crypt is off the hook. Just\n" "to verify, when you say without luks, you mean without any crypto bits\n" "in use at all on the filesystems postgres uses?\n" "\n" - "Usually the trick to reproducing filesystem corruptions is adding memory\n" + "Usually the trick to reproducing filesystem corruptions is adding memor=\n" + "y\n" "pressure. The corruption is probably a bad interaction between reads\n" "and writes, and we need to make sure the reads actually happen.\n" "\n" @@ -91,8 +106,9 @@ "\n" "-chris\n" "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-ext4\" in\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-ext4\" i=\n" + "n\n" "the body of a message to majordomo@vger.kernel.org\n" More majordomo info at http://vger.kernel.org/majordomo-info.html -d38ed89042f870228670cdaaddde9fbefee8a6f25a6b22389adbf6b2c62a216a +38d46ece56536e91aa0b7856d18a87504c79284dc78664e08f5b7f2f333617b0
diff --git a/a/1.txt b/N2/1.txt index 79f62f3..ccd3bd8 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -10,7 +10,7 @@ Excerpts from Jon Nelson's message of 2010-12-07 22:29:26 -0500: > >> >> >> >> visibility I've had into this via strace, what I see is zeroed pages > >> >> >> >> where there shouldn't be. > >> >> >> > -> >> >> >> > This sounds a lot like a bug higher up than dm-crypt. Â Zeros tend to +> >> >> >> > This sounds a lot like a bug higher up than dm-crypt. Zeros tend to > >> >> >> > come from some piece of code explicitly filling a page with zeros, and > >> >> >> > that often happens in the corner cases for O_DIRECT and a few other > >> >> >> > places in the filesystem. @@ -54,7 +54,3 @@ The idea is to trigger constant reads without having to swap heavily. 80% might be too much. -chris --- -To unsubscribe from this list: send the line "unsubscribe linux-ext4" 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 200a176..c02f76a 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -15,7 +15,7 @@ "ref\01291751698-sup-9297@think\0" "ref\0AANLkTin79GzUbfuZNKyTtqcyoUSO9AJimO77_ZOvqggH@mail.gmail.com\0" "ref\01291754340-sup-1631@think\0" - "ref\0 AANLkTim8uCmFK=LjkMmq_1O0KE3AiN_7g41AO0woxMv7@mail.gmail.com\0" + "ref\0AANLkTim8uCmFK=LjkMmq_1O0KE3AiN_7g41AO0woxMv7@mail.gmail.com\0" "ref\01291755258-sup-8760@think\0" "ref\0AANLkTi=OC9Z68U-j8s6vfU-_-6tkg5W7aUz9HEupidX9@mail.gmail.com\0" "From\0Chris Mason <chris.mason@oracle.com>\0" @@ -46,7 +46,7 @@ "> >> >> >> >> visibility I've had into this via strace, what I see is zeroed pages\n" "> >> >> >> >> where there shouldn't be.\n" "> >> >> >> >\n" - "> >> >> >> > This sounds a lot like a bug higher up than dm-crypt. \303\202\302\240Zeros tend to\n" + "> >> >> >> > This sounds a lot like a bug higher up than dm-crypt. \302\240Zeros tend to\n" "> >> >> >> > come from some piece of code explicitly filling a page with zeros, and\n" "> >> >> >> > that often happens in the corner cases for O_DIRECT and a few other\n" "> >> >> >> > places in the filesystem.\n" @@ -89,10 +89,6 @@ "The idea is to trigger constant reads without having to swap heavily.\n" "80% might be too much.\n" "\n" - "-chris\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-ext4\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + -chris -d38ed89042f870228670cdaaddde9fbefee8a6f25a6b22389adbf6b2c62a216a +8eda6aca8fade24b4c6f948a1e84108bb48650f856cea8101c59a695395ab684
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.