| To: | "Bernhard R. Erdmann" <be@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS & ADSM |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Mon, 2 Jul 2001 23:23:58 +0200 |
| Cc: | Andi Kleen <ak@xxxxxxx>, "Marcelo E. Magallon" <marcelo.magallon@xxxxxxxxxxx>, werner maes <werner.maes@xxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <3B40E5E3.CE1F0D6F@xxxxxxxxxxx>; from be@xxxxxxxxxxx on Mon, Jul 02, 2001 at 11:21:39PM +0200 |
| References: | <3.0.6.32.20010702115815.007fa190@xxxxxxxxxxxxxxxxxxxxxx> <20010702140752.A1180@xxxxxxxxxxxxxxx> <20010702192317.B6555@xxxxxxxxxxxxxxxxxxx> <3B40E5E3.CE1F0D6F@xxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Mon, Jul 02, 2001 at 11:21:39PM +0200, Bernhard R. Erdmann wrote: > > It's unfortunately not even an ADSM only problem. e.g. Arkeia has the > > same one and even VMWare checks file system types for some unknown > > reason. > > VMWare checks for locking capabilities - it doesn't know anything about > XFS as a filesystem but it prints a helpful error message to add > something to your blah.cfg and that helps. > > # Locking on XFS > host.FSSupportLocking1 = 0x58465342 They fixed that when reiserfs became popular. Older vmware wasn't that helpful. It is the wrong way anyways to check for locking, instead they should just do a autoconf style runtime check if it works and be generic. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS & ADSM, Bernhard R. Erdmann |
|---|---|
| Next by Date: | Re: fatal error -- couldn't initialize XFS library, Nathan Scott |
| Previous by Thread: | Re: XFS & ADSM, Bernhard R. Erdmann |
| Next by Thread: | Re: XFS & ADSM, Trond Hasle Amundsen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |