| To: | Andi Kleen <ak@xxxxxxx> |
|---|---|
| Subject: | Re: XFS & ADSM |
| From: | "Bernhard R. Erdmann" <be@xxxxxxxxxxx> |
| Date: | Mon, 02 Jul 2001 23:21:39 +0200 |
| Cc: | "Marcelo E. Magallon" <marcelo.magallon@xxxxxxxxxxx>, werner maes <werner.maes@xxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| References: | <3.0.6.32.20010702115815.007fa190@xxxxxxxxxxxxxxxxxxxxxx> <20010702140752.A1180@xxxxxxxxxxxxxxx> <20010702192317.B6555@xxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
> 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: ACL Support, Juergen Hasch |
|---|---|
| Next by Date: | Re: XFS & ADSM, Andi Kleen |
| Previous by Thread: | Re: XFS & ADSM, Andi Kleen |
| Next by Thread: | Re: XFS & ADSM, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |