| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS for postgres databases? |
| From: | Jeremy Jackson <jerj@xxxxxxxxxxxx> |
| Date: | Fri, 04 Jun 2004 16:05:53 -0400 |
| Cc: | Nathan Scott <nathans@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040512130047.A28089@xxxxxxxxxxxxx> |
| References: | <200405121300.14866.stevew@xxxxxxxxxxxxxxx> <1084332608.11308.3.camel@noodles> <20040512143941.A389759@xxxxxxxxxxxxxxxxxxxxxxxx> <200405121618.27843.ncunningham@xxxxxxxxxxxxx> <20040512165624.C389759@xxxxxxxxxxxxxxxxxxxxxxxx> <20040512130047.A28089@xxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1 |
Is there anything in the new 2.6 bio and queueing code that could
replace pagebufs entirely? That would seem ideal.
Christoph Hellwig wrote: On Wed, May 12, 2004 at 04:56:24PM +1000, Nathan Scott wrote: We can use a differnt mapping, in fact that's what XFS did before 2.4.10. It's a little bit of additional code, but not a big deal. The real problem with that is that now the blockdev mapping and XFS mapping are compltely unsynchonized, e.g. reading from the blockdev will give you stale data. For xfs_db this means it'll get access to an totally incoherent image of the filesystem. -- Jeremy Jackson Coplanar Networks (519)897-1516 http://www.coplanar.net |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS for postgres databases?, Jeremy Jackson |
|---|---|
| Next by Date: | Re: Scan after crash, AndyLiebman |
| Previous by Thread: | Re: XFS for postgres databases?, Jeffrey W. Baker |
| Next by Thread: | Re: XFS for postgres databases?, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |