| To: | Thomas Graichen <graichen@xxxxxxxxxxxxx>, thomas.graichen@xxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: stress test on ppc |
| From: | "Nathan Scott" <nathans@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 29 Nov 2000 09:40:41 -0400 |
| In-reply-to: | Thomas Graichen <news-innominate.list.sgi.xfs@innominate.de> "Re: stress test on ppc" (Nov 28, 10:37am) |
| References: | <news2mail-8uecj0$i5e$1@mate.bln.innominate.de> <10011110006.ZM127189@wobbly.melbourne.sgi.com> <news2mail-8uo7od$4lt$1@mate.bln.innominate.de> <10011141059.ZM128320@wobbly.melbourne.sgi.com> <news2mail-8utlfv$8iu$1@mate.bln.innominate.de> <10011221244.ZM158790@wobbly.melbourne.sgi.com> <news2mail-8vlq0n$hiu$2@mate.bln.innominate.de> <10011261336.ZM166460@wobbly.melbourne.sgi.com> <news2mail-8vt5ub$dhv$3@mate.bln.innominate.de> <10011281048.ZM165042@wobbly.melbourne.sgi.com> <news2mail-9001u3$n0b$2@mate.bln.innominate.de> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
hi,
On Nov 28, 10:37am, Thomas Graichen wrote:
> Subject: Re: stress test on ppc
> ...
> > so running xfs_db after doing mkfs.xfs with no blksize options
> > (as in test 004 - populate_scratch() routine) should always show
> > the blocksize as 4096. what i don't understand is how we've ended
> > up with a non-default (but valid) blocksize after doing a default
> > mkfs.
>
> hm - but mkfs.xfs is using the correct one:
>
> ...
> naming =version 2 bsize=4096
> log =internal log bsize=4096 blocks=1200
> ...
>
you snipped the interesting bit there - a couple of lines up
from "naming" ("data = bsize=????").
> so you assume that either xfs_db gets it wrong or it is stored some-
> how wrong on the filesystem (which i can't really believe due to how
> well xfs works on the ppc :-)?
>
;-)
i'm not sure where its going wrong - test 004 does a mkfs, mount,
a series of writes, umount, mount, and then runs xfs_db - could
be anywhere in that chain of events that the blksize goes loopy.
(could try running
"xfs_db -r -c sb -c p $SCRATCH_DEV | grep blocksize"
at each point to see where it goes wrong?)
cheers.
--
Nathan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | attr syscall on ppc, Thomas Graichen |
|---|---|
| Next by Date: | TAKE - module load copyright messages, Eric Sandeen |
| Previous by Thread: | Re: stress test on ppc, Thomas Graichen |
| Next by Thread: | Re: stress test on ppc, Thomas Graichen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |