diff for duplicates of <3000620.g91H2S8sUk@blindfold> diff --git a/a/1.txt b/N1/1.txt index 8ddceb8..33bfd37 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -33,3 +33,11 @@ fires at some point. Thanks, //richard + + + + + +______________________________________________________ +Linux MTD discussion mailing list +http://lists.infradead.org/mailman/listinfo/linux-mtd/ diff --git a/a/content_digest b/N1/content_digest index 527578d..34599fa 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,14 +4,14 @@ "Subject\0Re: Regression in handling power cuts since 3a1e819b4e80 (\"ovl: store file handle of lower inode on copy up\")\0" "Date\0Mon, 22 Oct 2018 10:26:29 +0200\0" "To\0Rafa\305\202 Mi\305\202ecki <zajec5@gmail.com>\0" - "Cc\0Amir Goldstein <amir73il@gmail.com>" - Miklos Szeredi <miklos@szeredi.hu> - linux-unionfs@vger.kernel.org - linux-fsdevel@vger.kernel.org - Artem Bityutskiy <dedekind1@gmail.com> + "Cc\0Artem Bityutskiy <dedekind1@gmail.com>" + Amir Goldstein <amir73il@gmail.com> Adrian Hunter <adrian.hunter@intel.com> + linux-unionfs@vger.kernel.org + Miklos Szeredi <miklos@szeredi.hu> linux-mtd@lists.infradead.org Russell Senior <russell@personaltelco.net> + linux-fsdevel@vger.kernel.org " OpenWrt Development List <openwrt-devel@lists.openwrt.org>\0" "\00:1\0" "b\0" @@ -49,6 +49,14 @@ "fires at some point.\n" "\n" "Thanks,\n" - //richard + "//richard\n" + "\n" + "\n" + "\n" + "\n" + "\n" + "______________________________________________________\n" + "Linux MTD discussion mailing list\n" + http://lists.infradead.org/mailman/listinfo/linux-mtd/ -608a229e7a7b46e41df39949fcdd466d339c63a8730bc881380069422f57523e +10669d3559860f7e69567f148c43da9645ce46225d810886848698a91d05e099
diff --git a/a/1.txt b/N2/1.txt index 8ddceb8..d77307f 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -24,7 +24,7 @@ Am Montag, 22. Oktober 2018, 09:14:08 CEST schrieb Rafał Miłecki: > By "Corruption" I mean file system corruption after power cut Well, is the filesystem not consistent anymore? -From what Russel explained to me, I thought the main problem is that no write back happens. +>From what Russel explained to me, I thought the main problem is that no write back happens. IOW the inode is present, has correct length, but no content is there (all zeros). Just like the typical case where userspace does not fsync. diff --git a/a/content_digest b/N2/content_digest index 527578d..cc71038 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -41,7 +41,7 @@ "> By \"Corruption\" I mean file system corruption after power cut\n" "\n" "Well, is the filesystem not consistent anymore?\n" - "From what Russel explained to me, I thought the main problem is that no write back happens.\n" + ">From what Russel explained to me, I thought the main problem is that no write back happens.\n" "IOW the inode is present, has correct length, but no content is there (all zeros).\n" "\n" "Just like the typical case where userspace does not fsync.\n" @@ -51,4 +51,4 @@ "Thanks,\n" //richard -608a229e7a7b46e41df39949fcdd466d339c63a8730bc881380069422f57523e +e803d5d9a6cebf489c87fc9eedd0190cef6fd16408359faf86d5741593416f60
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.