diff for duplicates of <20160425232552.GD18496@dastard> diff --git a/a/1.txt b/N1/1.txt index 51c7e47..e2ad6db 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -69,8 +69,7 @@ Dave. Dave Chinner david@fromorbit.com --- -To unsubscribe, send a message with 'unsubscribe linux-mm' in -the body to majordomo@kvack.org. For more info on Linux MM, -see: http://www.linux-mm.org/ . -Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a> +_______________________________________________ +xfs mailing list +xfs@oss.sgi.com +http://oss.sgi.com/mailman/listinfo/xfs diff --git a/a/content_digest b/N1/content_digest index 45ae3c1..c5facc9 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,21 +10,21 @@ "Date\0Tue, 26 Apr 2016 09:25:52 +1000\0" "To\0Verma" " Vishal L <vishal.l.verma@intel.com>\0" - "Cc\0hch@infradead.org <hch@infradead.org>" - Wilcox - Matthew R <matthew.r.wilcox@intel.com> + "Cc\0linux-block@vger.kernel.org <linux-block@vger.kernel.org>" + jack@suse.cz <jack@suse.cz> + axboe@fb.com <axboe@fb.com> + linux-nvdimm@ml01.01.org <linux-nvdimm@ml01.01.org> linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> - linux-block@vger.kernel.org <linux-block@vger.kernel.org> xfs@oss.sgi.com <xfs@oss.sgi.com> - linux-nvdimm@ml01.01.org <linux-nvdimm@ml01.01.org> - jmoyer@redhat.com <jmoyer@redhat.com> + hch@infradead.org <hch@infradead.org> linux-mm@kvack.org <linux-mm@kvack.org> - viro@zeniv.linux.org.uk <viro@zeniv.linux.org.uk> - axboe@fb.com <axboe@fb.com> - akpm@linux-foundation.org <akpm@linux-foundation.org> + jmoyer@redhat.com <jmoyer@redhat.com> + Wilcox + Matthew R <matthew.r.wilcox@intel.com> linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> + akpm@linux-foundation.org <akpm@linux-foundation.org> linux-ext4@vger.kernel.org <linux-ext4@vger.kernel.org> - " jack@suse.cz <jack@suse.cz>\0" + " viro@zeniv.linux.org.uk <viro@zeniv.linux.org.uk>\0" "\00:1\0" "b\0" "On Mon, Apr 25, 2016 at 05:14:36PM +0000, Verma, Vishal L wrote:\n" @@ -98,10 +98,9 @@ "Dave Chinner\n" "david@fromorbit.com\n" "\n" - "--\n" - "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n" - "the body to majordomo@kvack.org. For more info on Linux MM,\n" - "see: http://www.linux-mm.org/ .\n" - "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" + "_______________________________________________\n" + "xfs mailing list\n" + "xfs@oss.sgi.com\n" + http://oss.sgi.com/mailman/listinfo/xfs -1896f1bde51fb283d59ab60710b8f35e79be0a4f96fe3b38b828183eea637509 +d6e080f4cb58200fccebde7c35c7bce594dfd32cbc09aaaacb6cde0a3e36164d
diff --git a/a/1.txt b/N2/1.txt index 51c7e47..dcdd64a 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -9,7 +9,7 @@ On Mon, Apr 25, 2016 at 05:14:36PM +0000, Verma, Vishal L wrote: > > > -EIO in such cases so that the application doesn't lose the > > > information > > > that the bad block is actually causing the error. -> > EINVAL is a concern here. Not due to the right error reported, but +> > EINVAL is a concern here.��Not due to the right error reported, but > > because it means your current scheme is fundamentally broken - we > > need to support I/O at any alignment for DAX I/O, and not fail due to > > alignbment concernes for a highly specific degraded case. @@ -36,7 +36,7 @@ the owner of the bad sector? > - It write()s those sectors (possibly converted to file offsets using > fiemap) -> * This triggers the fallback path, but if the application is doing +> � � * This triggers the fallback path, but if the application is doing > this level of recovery, it will know the sector is bad, and write the > entire sector @@ -45,7 +45,7 @@ rewrite it? > - Or it replaces the entire file from backup also using write() (not > mmap+stores) -> * This just frees the fs block, and the next time the block is +> � � * This just frees the fs block, and the next time the block is > reallocated by the fs, it will likely be zeroed first, and that will be > done through the driver and will clear errors diff --git a/a/content_digest b/N2/content_digest index 45ae3c1..2bf5d24 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -38,7 +38,7 @@ "> > > -EIO in such cases so that the application doesn't lose the\n" "> > > information\n" "> > > that the bad block is actually causing the error.\n" - "> > EINVAL is a concern here.\302\240\302\240Not due to the right error reported, but\n" + "> > EINVAL is a concern here.\303\257\302\277\302\275\303\257\302\277\302\275Not due to the right error reported, but\n" "> > because it means your current scheme is fundamentally broken - we\n" "> > need to support I/O at any alignment for DAX I/O, and not fail due to\n" "> > alignbment concernes for a highly specific degraded case.\n" @@ -65,7 +65,7 @@ "\n" "> - It write()s those sectors (possibly converted to file offsets using\n" "> fiemap)\n" - "> \302\240 \302\240 * This triggers the fallback path, but if the application is doing\n" + "> \303\257\302\277\302\275 \303\257\302\277\302\275 * This triggers the fallback path, but if the application is doing\n" "> this level of recovery, it will know the sector is bad, and write the\n" "> entire sector\n" "\n" @@ -74,7 +74,7 @@ "\n" "> - Or it replaces the entire file from backup also using write() (not\n" "> mmap+stores)\n" - "> \302\240 \302\240 * This just frees the fs block, and the next time the block is\n" + "> \303\257\302\277\302\275 \303\257\302\277\302\275 * This just frees the fs block, and the next time the block is\n" "> reallocated by the fs, it will likely be zeroed first, and that will be\n" "> done through the driver and will clear errors\n" "\n" @@ -104,4 +104,4 @@ "see: http://www.linux-mm.org/ .\n" "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" -1896f1bde51fb283d59ab60710b8f35e79be0a4f96fe3b38b828183eea637509 +28c1bfaf49be45a68b12519b6c86d4398b7114f08cd7f25dc29795ef8a0b81ff
diff --git a/a/1.txt b/N3/1.txt index 51c7e47..7c5c8d3 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -9,7 +9,7 @@ On Mon, Apr 25, 2016 at 05:14:36PM +0000, Verma, Vishal L wrote: > > > -EIO in such cases so that the application doesn't lose the > > > information > > > that the bad block is actually causing the error. -> > EINVAL is a concern here. Not due to the right error reported, but +> > EINVAL is a concern here. Not due to the right error reported, but > > because it means your current scheme is fundamentally broken - we > > need to support I/O at any alignment for DAX I/O, and not fail due to > > alignbment concernes for a highly specific degraded case. @@ -36,7 +36,7 @@ the owner of the bad sector? > - It write()s those sectors (possibly converted to file offsets using > fiemap) -> * This triggers the fallback path, but if the application is doing +> * This triggers the fallback path, but if the application is doing > this level of recovery, it will know the sector is bad, and write the > entire sector @@ -45,7 +45,7 @@ rewrite it? > - Or it replaces the entire file from backup also using write() (not > mmap+stores) -> * This just frees the fs block, and the next time the block is +> * This just frees the fs block, and the next time the block is > reallocated by the fs, it will likely be zeroed first, and that will be > done through the driver and will clear errors diff --git a/a/content_digest b/N3/content_digest index 45ae3c1..56e0f66 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -38,7 +38,7 @@ "> > > -EIO in such cases so that the application doesn't lose the\n" "> > > information\n" "> > > that the bad block is actually causing the error.\n" - "> > EINVAL is a concern here.\302\240\302\240Not due to the right error reported, but\n" + "> > EINVAL is a concern here. Not due to the right error reported, but\n" "> > because it means your current scheme is fundamentally broken - we\n" "> > need to support I/O at any alignment for DAX I/O, and not fail due to\n" "> > alignbment concernes for a highly specific degraded case.\n" @@ -65,7 +65,7 @@ "\n" "> - It write()s those sectors (possibly converted to file offsets using\n" "> fiemap)\n" - "> \302\240 \302\240 * This triggers the fallback path, but if the application is doing\n" + "> * This triggers the fallback path, but if the application is doing\n" "> this level of recovery, it will know the sector is bad, and write the\n" "> entire sector\n" "\n" @@ -74,7 +74,7 @@ "\n" "> - Or it replaces the entire file from backup also using write() (not\n" "> mmap+stores)\n" - "> \302\240 \302\240 * This just frees the fs block, and the next time the block is\n" + "> * This just frees the fs block, and the next time the block is\n" "> reallocated by the fs, it will likely be zeroed first, and that will be\n" "> done through the driver and will clear errors\n" "\n" @@ -104,4 +104,4 @@ "see: http://www.linux-mm.org/ .\n" "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" -1896f1bde51fb283d59ab60710b8f35e79be0a4f96fe3b38b828183eea637509 +ffdabbda5ef4dd6493d0d335eefb0fcd7f4a95462675f5c4dd30b247b49da276
diff --git a/a/1.txt b/N4/1.txt index 51c7e47..8e50174 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -68,9 +68,3 @@ Dave. -- Dave Chinner david@fromorbit.com - --- -To unsubscribe, send a message with 'unsubscribe linux-mm' in -the body to majordomo@kvack.org. For more info on Linux MM, -see: http://www.linux-mm.org/ . -Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a> diff --git a/a/content_digest b/N4/content_digest index 45ae3c1..594ae7e 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -96,12 +96,6 @@ "Dave.\n" "-- \n" "Dave Chinner\n" - "david@fromorbit.com\n" - "\n" - "--\n" - "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n" - "the body to majordomo@kvack.org. For more info on Linux MM,\n" - "see: http://www.linux-mm.org/ .\n" - "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" + david@fromorbit.com -1896f1bde51fb283d59ab60710b8f35e79be0a4f96fe3b38b828183eea637509 +3c7fee198adb90612bb4d3ef0355ac6205c9d4d4c96ff80d9adff965002a1f41
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.