| To: | Linux XFS <linux-xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: lvm and segmentation |
| From: | Sean Neakums <sneakums@xxxxxxxx> |
| Date: | Fri, 22 Feb 2002 08:40:53 +0000 |
| In-reply-to: | <200202220745.g1M7jP631499@xxxxxxxxxxxxxxxxxxxxx> (monkeyiq's message of "Fri, 22 Feb 2002 17:45:25 +1000") |
| Mail-followup-to: | Linux XFS <linux-xfs@xxxxxxxxxxx> |
| References: | <200202220745.g1M7jP631499@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1 (i386-debian-linux-gnu) |
commence monkeyiq quotation: > I have been reading about lvm of late and was thinking of a possilbe > drawback to its use. > > It strikes me that a filesystem no longer knows about a contiguoius > disk the lvm and so if I define a preallocated 15Gb file then there > is no real say, even if xfs_bmap reports a single extent, that I can > be sure that there is a contiguious 15Gb block ready for my > data. Just wondering if I am correct in this thought? Sounds about right to me. If it *really* matters where your data ends up on disk (or even which disk it ends up on), you probably shouldn't be using LVM in the first place. -- ///////////////// | | The spark of a pin <sneakums@xxxxxxxx> | (require 'gnu) | dropping, falling feather-like. \\\\\\\\\\\\\\\\\ | | There is too much noise. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | bmv_oflags not being set, monkeyiq |
|---|---|
| Next by Date: | Re: linux-2.5.5-dj1 + xfs-cvs --- kernel bug at elevator.c : 237!, Zwane Mwaikambo |
| Previous by Thread: | lvm and segmentation, monkeyiq |
| Next by Thread: | Re: lvm and segmentation, Martin K. Petersen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |