| To: | Andi Kleen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree? |
| From: | Ragnar Kjørstad <xfs@xxxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 5 Jul 2001 23:41:37 +0200 |
| Cc: | kris buggenhout <buggenkr@xxxxxxxxxxxxxxxxxx>, Fang Han <dfbb@xxxxxxxxxxxx>, "linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <20010705101747.A32674@gruyere.muc.suse.de>; from Andi Kleen on Thu, Jul 05, 2001 at 10:17:47AM +0200 |
| References: | <20010705151357.A2773@dfbbb.cn.mvd> <3B4417D5.ECDC1125@god.bel.alcatel.be> <20010705101747.A32674@gruyere.muc.suse.de> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Thu, Jul 05, 2001 at 10:17:47AM +0200, Andi Kleen wrote: > All block devices in a XFS kernel need a special patch to add an ioctl > to set the logical block size. The original poster probably didn't add > that ioctl to his new hacked in LVM; which will cause all kinds of > problems with xfs user tools and also probably file system corruption. Is there a patch to add this ioctl to lvm? Exactly what filesystem corruption will it cause, and under what circumstances? If this is serious, maybe mkfs.xfs should refuse to build a filesystem on a device that doesn't support the ioctl? -- Ragnar Kjorstad Big Storage |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE - merge up to 2.4.7-pre3, Steve Lord |
|---|---|
| Next by Date: | Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree?, Andi Kleen |
| Previous by Thread: | Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree?, Andi Kleen |
| Next by Thread: | Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree?, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |