| To: | pgf111000 <junkmail@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] mkfs.xfs, lvm, multi-terrabyte hardware array and luks |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Tue, 20 Feb 2007 14:58:17 -0600 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <9069238.post@xxxxxxxxxxxxxxx> |
| References: | <9068053.post@xxxxxxxxxxxxxxx> <45DB4CE1.3040302@xxxxxxxxxxx> <9069238.post@xxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 1.5.0.9 (X11/20070212) |
pgf111000 wrote: > Thank you for the quick response. I have posted on a few luks forums to try > to delve into this issue a little deeper; if they are aware of a resolution > I'll make sure to post it. The interesting thing is that when I mkfs.ext3 > on luks partitions above 2-3gb all is fine; I wish xfs and luks would play > nice..... mkfs.xfs actually does writes out at the end of the device and verifies them; I'm not sure ext3 is doing the same. You may find yourself in trouble on ext3 post-mkfs (or you may not...) I seem to recall that xfs has shaken out similar problems on other block devices for this reason. I'd do some simple device-level read/write tests around 2GB just for fun, see how it goes. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] mkfs.xfs, lvm, multi-terrabyte hardware array and luks, pgf111000 |
|---|---|
| Next by Date: | Re: xfsdump/xfsrestore question, Timothy Shimmin |
| Previous by Thread: | Re: [PATCH] mkfs.xfs, lvm, multi-terrabyte hardware array and luks, pgf111000 |
| Next by Thread: | Re: [PATCH] mkfs.xfs, lvm, multi-terrabyte hardware array and luks, pgf111000 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |