| To: | kris buggenhout <gast6@xxxxxx> |
|---|---|
| Subject: | Re: XFS on sparc 64 |
| From: | "Martin K. Petersen" <mkp@xxxxxxxxxxxxx> |
| Date: | 20 Nov 2000 21:24:15 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | kris buggenhout's message of "Mon, 20 Nov 2000 10:29:01 +0100" |
| Organization: | Linuxcare, Inc. |
| References: | <200011162105.PAA21883@jen.americas.sgi.com> <3A14F45E.A844533C@vum.be> <3A1548CA.71E44765@thebarn.com> <3A18EEDD.A313D46D@vum.be> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) |
Just a note regarding XFS on sparc64. We've previously seen file system corruption due to the fact that there was no way to set the device block size from userland. I fixed this some time ago by adding a BLKSETSIZE ioctl. Linux on UltraSPARC is a bit tricky, however, (32-bit userland on 64-bit kernel) and as it turns out I hadn't added the new ioctl to the sparc64 argument conversion list. I just fixed that. You'll need to recreate your file systems to make sure that everything is properly aligned. Please let me know whether this improves things for you. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@xxxxxxxxxxxxx, http://www.linuxcare.com/ Linuxcare. Moving Forward. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | ADD 808328 - xfs_support EXPORTs symbols with generic names, cattelan@xxxxxxxxxxx |
|---|---|
| Next by Date: | TAKE 808315 - Full file systems can become corrupted with XFS Linux., lord@xxxxxxx |
| Previous by Thread: | Re: XFS on sparc 64, kris buggenhout |
| Next by Thread: | Re: XFS on sparc 64, Martin K. Petersen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |