diff for duplicates of <1484961537.2029.22.camel@hpe.com> diff --git a/a/1.txt b/N1/1.txt index 428fb46..1aaf465 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,20 +1,28 @@ -T24gRnJpLCAyMDE3LTAxLTIwIGF0IDE4OjI0ICswOTAwLCBZYXN1bm9yaSBHb3RvIHdyb3RlOg0K -IDoNCj4gPiANCj4gPiBMaWtlIG1lbnRpb25lZCBiZWZvcmUsIHRoaXMgZGlzY3Vzc2lvbiBpcyBt -b3JlIGFib3V0IHByZXNlbnRhdGlvbg0KPiA+IG9mIGVycm9ycyBpbiBhIGtub3duIGNvbnN1bWFi -bGUgZm9ybWF0LCByYXRoZXIgdGhhbiByZWNvdmVyaW5nIGZyb20NCj4gPiBlcnJvcnMuIFdoaWxl -IHJlY292ZXJpbmcgZnJvbSBlcnJvcnMgaXMgaW50ZXJlc3RpbmcsIHdlIGFscmVhZHkNCj4gPiBo -YXZlIGxheWVycyBsaWtlIFJBSUQgZm9yIHRoYXQsIGFuZCB0aGV5IGFyZSBhcyBhcHBsaWNhYmxl -IHRvDQo+ID4gTlZESU1NIGJhY2tlZCBzdG9yYWdlIGFzIHRoZXkgaGF2ZSBiZWVuIGZvciBkaXNr -L1NTRCBiYXNlZCBzdG9yYWdlLg0KPiANCj4gSSBoYXZlIG9uZSBxdWVzdGlvbiBoZXJlLg0KPiAN -Cj4gQ2VydGFpbmx5LCB1c2VyIGNhbiB1c2UgTFZNIG1pcnJvcmluZyBmb3Igc3RvcmFnZSBtb2Rl -IG9mIE5WRElNTS4NCj4gSG93ZXZlciwgTlZESU1NIGhhcyBEQVggbW9kZS7CoA0KPiBDYW4gdXNl -ciB1c2UgTFZNIG1pcnJvcmluZyBmb3IgTlZESU1NIERBWCBtb2RlPw0KPiBJIGNvdWxkIG5vdCBm -aW5kIGFueSBpbmZvcm1hdGlvbiB0aGF0IExWTSBzdXBwb3J0IERBWC4uLi4NCg0KZG0tbGluZWFy -IGFuZCBkbS1zdHJpcGUgc3VwcG9ydCBEQVguICBUaGlzIGlzIGRvbmUgYnkgbWFwcGluZyBibG9j -aw0KYWxsb2NhdGlvbnMgdG8gTFZNIHBoeXNpY2FsIGRldmljZXMuICBPbmNlIGJsb2NrcyBhcmUg -YWxsb2NhdGVkLCBhbGwNCkRBWCBJL09zIGFyZSBkaXJlY3QgYW5kIGRvIG5vdCBnbyB0aHJvdWdo -IHRoZSBkZXZpY2UtbWFwcGVyIGxheWVyLiAgV2UNCm1heSBiZSBhYmxlIHRvIGNoYW5nZSBpdCBm -b3IgcmVhZC93cml0ZSBwYXRocywgYnV0IGl0IHJlbWFpbnMgdHJ1ZSBmb3INCm1tYXAuICBTbywg -SSBkbyBub3QgdGhpbmsgREFYIGNhbiBiZSBzdXBwb3J0ZWQgd2l0aCBMVk0gbWlycm9yaW5nLiAN -ClRoaXMgZG9lcyBub3QgcHJlY2x1ZGUgaGFyZHdhcmUgbWlycm9yaW5nLCB0aG91Z2guDQoNCi1U -b3NoaQ0K +On Fri, 2017-01-20 at 18:24 +0900, Yasunori Goto wrote: + : +> > +> > Like mentioned before, this discussion is more about presentation +> > of errors in a known consumable format, rather than recovering from +> > errors. While recovering from errors is interesting, we already +> > have layers like RAID for that, and they are as applicable to +> > NVDIMM backed storage as they have been for disk/SSD based storage. +> +> I have one question here. +> +> Certainly, user can use LVM mirroring for storage mode of NVDIMM. +> However, NVDIMM has DAX mode. +> Can user use LVM mirroring for NVDIMM DAX mode? +> I could not find any information that LVM support DAX.... + +dm-linear and dm-stripe support DAX. This is done by mapping block +allocations to LVM physical devices. Once blocks are allocated, all +DAX I/Os are direct and do not go through the device-mapper layer. We +may be able to change it for read/write paths, but it remains true for +mmap. So, I do not think DAX can be supported with LVM mirroring. +This does not preclude hardware mirroring, though. + +-Toshi +_______________________________________________ +Linux-nvdimm mailing list +Linux-nvdimm@lists.01.org +https://lists.01.org/mailman/listinfo/linux-nvdimm diff --git a/a/content_digest b/N1/content_digest index 4092608..917840e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,41 +1,50 @@ "ref\0CAL4pJv6MvJhTuPJbPAV-HXGrMST-dJs461O=wwfcpdvQA-amdA@mail.gmail.com\0" "ref\020170120004633.GA14128@omniknight.lm.intel.com\0" "ref\020170120182435.0E12.E1E9C6FF@jp.fujitsu.com\0" - "From\0Kani, Toshimitsu <toshi.kani@hpe.com>\0" + "ref\020170120182435.0E12.E1E9C6FF-+CUm20s59erQFUHtdCDX3A@public.gmane.org\0" + "From\0Kani, Toshimitsu <toshi.kani-ZPxbGqLxI0U@public.gmane.org>\0" "Subject\0Re: [LSF/MM TOPIC] Badblocks checking/representation in filesystems\0" "Date\0Sat, 21 Jan 2017 00:23:24 +0000\0" - "To\0y-goto@jp.fujitsu.com <y-goto@jp.fujitsu.com>" - " vishal.l.verma@intel.com <vishal.l.verma@intel.com>\0" - "Cc\0Vyacheslav.Dubeyko@wdc.com <Vyacheslav.Dubeyko@wdc.com>" - linux-block@vger.kernel.org <linux-block@vger.kernel.org> - lsf-pc@lists.linux-foundation.org <lsf-pc@lists.linux-foundation.org> - linux-nvdimm@ml01.01.org <linux-nvdimm@ml01.01.org> - slava@dubeyko.com <slava@dubeyko.com> - adilger@dilger.ca <adilger@dilger.ca> - darrick.wong@oracle.com <darrick.wong@oracle.com> - linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> - " andiry@gmail.com <andiry@gmail.com>\0" + "To\0y-goto-+CUm20s59erQFUHtdCDX3A@public.gmane.org <y-goto-+CUm20s59erQFUHtdCDX3A@public.gmane.org>" + " vishal.l.verma-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org <vishal.l.verma-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>\0" + "Cc\0adilger-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org <adilger-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org>" + Vyacheslav.Dubeyko-Sjgp3cTcYWE@public.gmane.org <Vyacheslav.Dubeyko-Sjgp3cTcYWE@public.gmane.org> + darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org <darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> + linux-nvdimm-y27Ovi1pjclAfugRpC6u6w@public.gmane.org <linux-nvdimm-y27Ovi1pjclAfugRpC6u6w@public.gmane.org> + linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + andiry-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <andiry-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> + slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org> + linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + " lsf-pc-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org <lsf-pc-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>\0" "\00:1\0" "b\0" - "T24gRnJpLCAyMDE3LTAxLTIwIGF0IDE4OjI0ICswOTAwLCBZYXN1bm9yaSBHb3RvIHdyb3RlOg0K\n" - "IDoNCj4gPiANCj4gPiBMaWtlIG1lbnRpb25lZCBiZWZvcmUsIHRoaXMgZGlzY3Vzc2lvbiBpcyBt\n" - "b3JlIGFib3V0IHByZXNlbnRhdGlvbg0KPiA+IG9mIGVycm9ycyBpbiBhIGtub3duIGNvbnN1bWFi\n" - "bGUgZm9ybWF0LCByYXRoZXIgdGhhbiByZWNvdmVyaW5nIGZyb20NCj4gPiBlcnJvcnMuIFdoaWxl\n" - "IHJlY292ZXJpbmcgZnJvbSBlcnJvcnMgaXMgaW50ZXJlc3RpbmcsIHdlIGFscmVhZHkNCj4gPiBo\n" - "YXZlIGxheWVycyBsaWtlIFJBSUQgZm9yIHRoYXQsIGFuZCB0aGV5IGFyZSBhcyBhcHBsaWNhYmxl\n" - "IHRvDQo+ID4gTlZESU1NIGJhY2tlZCBzdG9yYWdlIGFzIHRoZXkgaGF2ZSBiZWVuIGZvciBkaXNr\n" - "L1NTRCBiYXNlZCBzdG9yYWdlLg0KPiANCj4gSSBoYXZlIG9uZSBxdWVzdGlvbiBoZXJlLg0KPiAN\n" - "Cj4gQ2VydGFpbmx5LCB1c2VyIGNhbiB1c2UgTFZNIG1pcnJvcmluZyBmb3Igc3RvcmFnZSBtb2Rl\n" - "IG9mIE5WRElNTS4NCj4gSG93ZXZlciwgTlZESU1NIGhhcyBEQVggbW9kZS7CoA0KPiBDYW4gdXNl\n" - "ciB1c2UgTFZNIG1pcnJvcmluZyBmb3IgTlZESU1NIERBWCBtb2RlPw0KPiBJIGNvdWxkIG5vdCBm\n" - "aW5kIGFueSBpbmZvcm1hdGlvbiB0aGF0IExWTSBzdXBwb3J0IERBWC4uLi4NCg0KZG0tbGluZWFy\n" - "IGFuZCBkbS1zdHJpcGUgc3VwcG9ydCBEQVguICBUaGlzIGlzIGRvbmUgYnkgbWFwcGluZyBibG9j\n" - "aw0KYWxsb2NhdGlvbnMgdG8gTFZNIHBoeXNpY2FsIGRldmljZXMuICBPbmNlIGJsb2NrcyBhcmUg\n" - "YWxsb2NhdGVkLCBhbGwNCkRBWCBJL09zIGFyZSBkaXJlY3QgYW5kIGRvIG5vdCBnbyB0aHJvdWdo\n" - "IHRoZSBkZXZpY2UtbWFwcGVyIGxheWVyLiAgV2UNCm1heSBiZSBhYmxlIHRvIGNoYW5nZSBpdCBm\n" - "b3IgcmVhZC93cml0ZSBwYXRocywgYnV0IGl0IHJlbWFpbnMgdHJ1ZSBmb3INCm1tYXAuICBTbywg\n" - "SSBkbyBub3QgdGhpbmsgREFYIGNhbiBiZSBzdXBwb3J0ZWQgd2l0aCBMVk0gbWlycm9yaW5nLiAN\n" - "ClRoaXMgZG9lcyBub3QgcHJlY2x1ZGUgaGFyZHdhcmUgbWlycm9yaW5nLCB0aG91Z2guDQoNCi1U\n" - b3NoaQ0K + "On Fri, 2017-01-20 at 18:24 +0900, Yasunori Goto wrote:\n" + " :\n" + "> > \n" + "> > Like mentioned before, this discussion is more about presentation\n" + "> > of errors in a known consumable format, rather than recovering from\n" + "> > errors. While recovering from errors is interesting, we already\n" + "> > have layers like RAID for that, and they are as applicable to\n" + "> > NVDIMM backed storage as they have been for disk/SSD based storage.\n" + "> \n" + "> I have one question here.\n" + "> \n" + "> Certainly, user can use LVM mirroring for storage mode of NVDIMM.\n" + "> However, NVDIMM has DAX mode.\302\240\n" + "> Can user use LVM mirroring for NVDIMM DAX mode?\n" + "> I could not find any information that LVM support DAX....\n" + "\n" + "dm-linear and dm-stripe support DAX. This is done by mapping block\n" + "allocations to LVM physical devices. Once blocks are allocated, all\n" + "DAX I/Os are direct and do not go through the device-mapper layer. We\n" + "may be able to change it for read/write paths, but it remains true for\n" + "mmap. So, I do not think DAX can be supported with LVM mirroring. \n" + "This does not preclude hardware mirroring, though.\n" + "\n" + "-Toshi\n" + "_______________________________________________\n" + "Linux-nvdimm mailing list\n" + "Linux-nvdimm@lists.01.org\n" + https://lists.01.org/mailman/listinfo/linux-nvdimm -c8a6f164751a47973bbb773a2a5dcf2f4c508bd8292bd78d98d9fecb3d25c4cc +6ea6c4af3dac988befeda7c671d567228d141e8835bdcbc45068e92f18d9660a
diff --git a/a/1.txt b/N2/1.txt index 428fb46..668a3e4 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,20 +1,24 @@ -T24gRnJpLCAyMDE3LTAxLTIwIGF0IDE4OjI0ICswOTAwLCBZYXN1bm9yaSBHb3RvIHdyb3RlOg0K -IDoNCj4gPiANCj4gPiBMaWtlIG1lbnRpb25lZCBiZWZvcmUsIHRoaXMgZGlzY3Vzc2lvbiBpcyBt -b3JlIGFib3V0IHByZXNlbnRhdGlvbg0KPiA+IG9mIGVycm9ycyBpbiBhIGtub3duIGNvbnN1bWFi -bGUgZm9ybWF0LCByYXRoZXIgdGhhbiByZWNvdmVyaW5nIGZyb20NCj4gPiBlcnJvcnMuIFdoaWxl -IHJlY292ZXJpbmcgZnJvbSBlcnJvcnMgaXMgaW50ZXJlc3RpbmcsIHdlIGFscmVhZHkNCj4gPiBo -YXZlIGxheWVycyBsaWtlIFJBSUQgZm9yIHRoYXQsIGFuZCB0aGV5IGFyZSBhcyBhcHBsaWNhYmxl -IHRvDQo+ID4gTlZESU1NIGJhY2tlZCBzdG9yYWdlIGFzIHRoZXkgaGF2ZSBiZWVuIGZvciBkaXNr -L1NTRCBiYXNlZCBzdG9yYWdlLg0KPiANCj4gSSBoYXZlIG9uZSBxdWVzdGlvbiBoZXJlLg0KPiAN -Cj4gQ2VydGFpbmx5LCB1c2VyIGNhbiB1c2UgTFZNIG1pcnJvcmluZyBmb3Igc3RvcmFnZSBtb2Rl -IG9mIE5WRElNTS4NCj4gSG93ZXZlciwgTlZESU1NIGhhcyBEQVggbW9kZS7CoA0KPiBDYW4gdXNl -ciB1c2UgTFZNIG1pcnJvcmluZyBmb3IgTlZESU1NIERBWCBtb2RlPw0KPiBJIGNvdWxkIG5vdCBm -aW5kIGFueSBpbmZvcm1hdGlvbiB0aGF0IExWTSBzdXBwb3J0IERBWC4uLi4NCg0KZG0tbGluZWFy -IGFuZCBkbS1zdHJpcGUgc3VwcG9ydCBEQVguICBUaGlzIGlzIGRvbmUgYnkgbWFwcGluZyBibG9j -aw0KYWxsb2NhdGlvbnMgdG8gTFZNIHBoeXNpY2FsIGRldmljZXMuICBPbmNlIGJsb2NrcyBhcmUg -YWxsb2NhdGVkLCBhbGwNCkRBWCBJL09zIGFyZSBkaXJlY3QgYW5kIGRvIG5vdCBnbyB0aHJvdWdo -IHRoZSBkZXZpY2UtbWFwcGVyIGxheWVyLiAgV2UNCm1heSBiZSBhYmxlIHRvIGNoYW5nZSBpdCBm -b3IgcmVhZC93cml0ZSBwYXRocywgYnV0IGl0IHJlbWFpbnMgdHJ1ZSBmb3INCm1tYXAuICBTbywg -SSBkbyBub3QgdGhpbmsgREFYIGNhbiBiZSBzdXBwb3J0ZWQgd2l0aCBMVk0gbWlycm9yaW5nLiAN -ClRoaXMgZG9lcyBub3QgcHJlY2x1ZGUgaGFyZHdhcmUgbWlycm9yaW5nLCB0aG91Z2guDQoNCi1U -b3NoaQ0K +On Fri, 2017-01-20 at 18:24 +0900, Yasunori Goto wrote: + : +> > +> > Like mentioned before, this discussion is more about presentation +> > of errors in a known consumable format, rather than recovering from +> > errors. While recovering from errors is interesting, we already +> > have layers like RAID for that, and they are as applicable to +> > NVDIMM backed storage as they have been for disk/SSD based storage. +> +> I have one question here. +> +> Certainly, user can use LVM mirroring for storage mode of NVDIMM. +> However, NVDIMM has DAX mode. +> Can user use LVM mirroring for NVDIMM DAX mode? +> I could not find any information that LVM support DAX.... + +dm-linear and dm-stripe support DAX. This is done by mapping block +allocations to LVM physical devices. Once blocks are allocated, all +DAX I/Os are direct and do not go through the device-mapper layer. We +may be able to change it for read/write paths, but it remains true for +mmap. So, I do not think DAX can be supported with LVM mirroring. +This does not preclude hardware mirroring, though. + +-Toshi diff --git a/a/content_digest b/N2/content_digest index 4092608..9aaf59e 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -17,25 +17,29 @@ " andiry@gmail.com <andiry@gmail.com>\0" "\00:1\0" "b\0" - "T24gRnJpLCAyMDE3LTAxLTIwIGF0IDE4OjI0ICswOTAwLCBZYXN1bm9yaSBHb3RvIHdyb3RlOg0K\n" - "IDoNCj4gPiANCj4gPiBMaWtlIG1lbnRpb25lZCBiZWZvcmUsIHRoaXMgZGlzY3Vzc2lvbiBpcyBt\n" - "b3JlIGFib3V0IHByZXNlbnRhdGlvbg0KPiA+IG9mIGVycm9ycyBpbiBhIGtub3duIGNvbnN1bWFi\n" - "bGUgZm9ybWF0LCByYXRoZXIgdGhhbiByZWNvdmVyaW5nIGZyb20NCj4gPiBlcnJvcnMuIFdoaWxl\n" - "IHJlY292ZXJpbmcgZnJvbSBlcnJvcnMgaXMgaW50ZXJlc3RpbmcsIHdlIGFscmVhZHkNCj4gPiBo\n" - "YXZlIGxheWVycyBsaWtlIFJBSUQgZm9yIHRoYXQsIGFuZCB0aGV5IGFyZSBhcyBhcHBsaWNhYmxl\n" - "IHRvDQo+ID4gTlZESU1NIGJhY2tlZCBzdG9yYWdlIGFzIHRoZXkgaGF2ZSBiZWVuIGZvciBkaXNr\n" - "L1NTRCBiYXNlZCBzdG9yYWdlLg0KPiANCj4gSSBoYXZlIG9uZSBxdWVzdGlvbiBoZXJlLg0KPiAN\n" - "Cj4gQ2VydGFpbmx5LCB1c2VyIGNhbiB1c2UgTFZNIG1pcnJvcmluZyBmb3Igc3RvcmFnZSBtb2Rl\n" - "IG9mIE5WRElNTS4NCj4gSG93ZXZlciwgTlZESU1NIGhhcyBEQVggbW9kZS7CoA0KPiBDYW4gdXNl\n" - "ciB1c2UgTFZNIG1pcnJvcmluZyBmb3IgTlZESU1NIERBWCBtb2RlPw0KPiBJIGNvdWxkIG5vdCBm\n" - "aW5kIGFueSBpbmZvcm1hdGlvbiB0aGF0IExWTSBzdXBwb3J0IERBWC4uLi4NCg0KZG0tbGluZWFy\n" - "IGFuZCBkbS1zdHJpcGUgc3VwcG9ydCBEQVguICBUaGlzIGlzIGRvbmUgYnkgbWFwcGluZyBibG9j\n" - "aw0KYWxsb2NhdGlvbnMgdG8gTFZNIHBoeXNpY2FsIGRldmljZXMuICBPbmNlIGJsb2NrcyBhcmUg\n" - "YWxsb2NhdGVkLCBhbGwNCkRBWCBJL09zIGFyZSBkaXJlY3QgYW5kIGRvIG5vdCBnbyB0aHJvdWdo\n" - "IHRoZSBkZXZpY2UtbWFwcGVyIGxheWVyLiAgV2UNCm1heSBiZSBhYmxlIHRvIGNoYW5nZSBpdCBm\n" - "b3IgcmVhZC93cml0ZSBwYXRocywgYnV0IGl0IHJlbWFpbnMgdHJ1ZSBmb3INCm1tYXAuICBTbywg\n" - "SSBkbyBub3QgdGhpbmsgREFYIGNhbiBiZSBzdXBwb3J0ZWQgd2l0aCBMVk0gbWlycm9yaW5nLiAN\n" - "ClRoaXMgZG9lcyBub3QgcHJlY2x1ZGUgaGFyZHdhcmUgbWlycm9yaW5nLCB0aG91Z2guDQoNCi1U\n" - b3NoaQ0K + "On Fri, 2017-01-20 at 18:24 +0900, Yasunori Goto wrote:\n" + " :\n" + "> > \n" + "> > Like mentioned before, this discussion is more about presentation\n" + "> > of errors in a known consumable format, rather than recovering from\n" + "> > errors. While recovering from errors is interesting, we already\n" + "> > have layers like RAID for that, and they are as applicable to\n" + "> > NVDIMM backed storage as they have been for disk/SSD based storage.\n" + "> \n" + "> I have one question here.\n" + "> \n" + "> Certainly, user can use LVM mirroring for storage mode of NVDIMM.\n" + "> However, NVDIMM has DAX mode.\302\240\n" + "> Can user use LVM mirroring for NVDIMM DAX mode?\n" + "> I could not find any information that LVM support DAX....\n" + "\n" + "dm-linear and dm-stripe support DAX. This is done by mapping block\n" + "allocations to LVM physical devices. Once blocks are allocated, all\n" + "DAX I/Os are direct and do not go through the device-mapper layer. We\n" + "may be able to change it for read/write paths, but it remains true for\n" + "mmap. So, I do not think DAX can be supported with LVM mirroring. \n" + "This does not preclude hardware mirroring, though.\n" + "\n" + -Toshi -c8a6f164751a47973bbb773a2a5dcf2f4c508bd8292bd78d98d9fecb3d25c4cc +0fdc243109ec70410adeb389ea13fc6e1761b127ec58e2ef61bc06ba07a44eaa
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.