[just as a pre-info: i currently try to get the sfi xfs filesystem
running on non x86 architectures - got to the point of a kernel bug
on the ppc for which i have a fix now and hope that it works this
evening then i try it and now tried the alpha ... keep in mind that
this is still code under development - so don't expect anything
useful out of the box here on the alpha - but if you like to help
me testing and maybe debugging this to get a good filesystem for
the alpha just read on and have a look at the sgi xfs list]
ok - just tried the next one :-)
kernel builds fine (with the below patch - what are the double under-
scored types btw.?) and i was able to mount the filesystem instantly
without a problem - i also was able to copy the whole /etc tree over
to it and remove it again - the try to compile bonnie for running it
resulted in a pagebuf error (but no crash - only a fs shutdown due
to an io error) - so it looks quite promising - also there were some
compile time warnings which i'll look through carefully - maybe it's
in there anywhere ... also debugging the pagebuf stuff should be
a bit easier now that there is also kdb less pagebuf tracing from
the ppc here (btw.: any chance to get this included into the tree if
i clean it up a bit? - i think it might be a good help for new kdbless
arches)
more details about any errors i cannot resolve i will post after
the weekend (it's time for a break now :-)
looks like it gets time that the mkfs and repair commands get more
easily compilable on other arches too so that one can play around
with real filesystems instead of my 32mb image ... is there any
> timeframe planned for the cleanup of those two tools ?
ok - for anyone who want to help getting this working (i'll post this
to the alpha list too - maybe someone there will help too) - just
pick up the sources from oss.sgi.com's cvs tree (linux-2.4-xfs) and
my patches from
http://innominate.org/~graichen/projects/xfs-ppc/diff.000802
(don't get confused by the ppc - they are good for the alpha too and
gives the pagebuf tracing for debugging :-) and have a look at the sgi
xfs list (details you can also find at oss.sgi.com)
so far thanks for the sgi guys for providing a - so far - very arch-
portable code as it looks like
t
--- fs/xfs/xfs_error.c 2000/06/09 06:40:03 1.27
+++ fs/xfs/xfs_error.c 2000/08/04 06:39:39
@@ -213,7 +213,7 @@
}
int
-xfs_errortag_clearall_umount(int64_t fsid, char *fsname, int loud)
+xfs_errortag_clearall_umount(__int64_t fsid, char *fsname, int loud)
{
int i;
int cleared = 0;
@@ -278,7 +278,7 @@
}
void
-xfs_cmn_err(uint64_t panic_tag, int level, xfs_mount_t *mp, char *fmt,
+xfs_cmn_err(__uint64_t panic_tag, int level, xfs_mount_t *mp, char *fmt
{
va_list ap;
--
[EMAIL PROTECTED]
Technical Director innominate AG
Clustering & Security networking people
tel: +49.30.308806-13 fax: -77 http://innominate.de
