| To: | "L.A. Walsh" <xfs@xxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: why crc req on free-inobt & file-type-indir options? |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Thu, 06 Aug 2015 22:36:07 -0700 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <55C41D75.4040504@xxxxxxxxx> |
| References: | <55C41D75.4040504@xxxxxxxxx> |
On 8/6/15 7:52 PM, L.A. Walsh wrote: > > Could anyone point me at the discussion or literature as to why > a free-inodeB-Tree and inline-types, should *REQUIRE* a -crc=1 option? FWIW, you can enable ftype w/o crcs. Today it's a little broken, if you specify in the wrong order it fails. I just sent a patch for that. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] mkfs.xfs: fix ftype-vs-crc option combination testing, Eric Sandeen |
|---|---|
| Next by Date: | Re: why crc req on free-inobt & file-type-indir options?, L.A. Walsh |
| Previous by Thread: | Re: why crc req on free-inobt & file-type-indir options?, L.A. Walsh |
| Next by Thread: | why crc req on free-inobt & file-type-indir options?, L.A. Walsh |
| Indexes: | [Date] [Thread] [Top] [All Lists] |