[Top] [All Lists]

Re: stress test on ppc

To: linux-xfs@xxxxxxxxxxx
Subject: Re: stress test on ppc
From: Thomas Graichen <news-innominate.list.sgi.xfs@xxxxxxxxxxxxx>
Date: 28 Nov 2000 10:37:55 GMT
Distribution: local
Organization: innominate AG, Berlin, Germany
References: <news2mail-8uecj0$i5e$1@xxxxxxxxxxxxxxxxxxxxxx> <10011110006.ZM127189@xxxxxxxxxxxxxxxxxxxxxxxx> <news2mail-8uo7od$4lt$1@xxxxxxxxxxxxxxxxxxxxxx> <10011141059.ZM128320@xxxxxxxxxxxxxxxxxxxxxxxx> <news2mail-8utlfv$8iu$1@xxxxxxxxxxxxxxxxxxxxxx> <10011221244.ZM158790@xxxxxxxxxxxxxxxxxxxxxxxx> <news2mail-8vlq0n$hiu$2@xxxxxxxxxxxxxxxxxxxxxx> <10011261336.ZM166460@xxxxxxxxxxxxxxxxxxxxxxxx> <news2mail-8vt5ub$dhv$3@xxxxxxxxxxxxxxxxxxxxxx> <10011281048.ZM165042@xxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Thomas Graichen <graichen@xxxxxxxxxxxxx>
Reply-to: thomas.graichen@xxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.0-XFS-test10 (i686))
"Nathan Scott" <nathans@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> no, thats not it.  the (filesystem) blocksize comes from mkfs.xfs
> and is written into all of the superblocks using the value which
> mkfs calculates.  By default (which is the case, in test 004)
> this is (1<<XFS_DFL_BLOCKSIZE_LOG)... 4096.  you could trace the
> value of the "blocksize" variable in xfs_mkfs.c ... it eventually
> gets stuffed into the primary sb (line 1390) and written to disk
> (line 1499).

> 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

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 :-)?

>> ppc:/usr/src/xfs/cmd/xfs/stress # mount /dev/hda9 /mnt

> yup - thats it ... looks like your mount does auto-detect
> minix somehow.  hmmm... i'll need to go see whats different
> between your mount code and the mkfs/mountinfo.c code.  which
> version of mount are you using?  (mount -V?)

ppc:~ # mount -V
mount: mount-2.10m
ppc:~ #

>> btw. i'm not shure if it really is only usermode - i think at least
>> the suse mount seems to require fs support (maybe looking into
>> /proc/filesystems - suse has no /etc/filesystems for instance) for
>> the mount fs detection - otherwise you get a "wrong major ..."

> is Suse mount based on Andries Brouwers' util-linux mount code?
> I'd be surprised if not.  This looks in all sorts of places to
> try and figure out the filesystem type (including procfs & /etc,
> but also by probing).   Its this probing code which mkfs.xfs
> uses in order to try not write on an existing filesystem.

ppc:~ # rpm -qf /bin/mount        
ppc:~ # rpm -qi util-2.10m-61
Name        : util                         Relocations: (not relocateable)
Version     : 2.10m                             Vendor: SuSE GmbH, Nuernberg, Ge
Release     : 61                            Build Date: Tue Sep 19 03:41:24 2000
Install date: Fri Nov 17 08:54:44 2000      Build Host: papaya.suse.de
Group       : System Environment/Base       Source RPM: util-2.10m-61.src.rpm
Size        : 2497677                          License: GPL/BSD/Sun Microsystems
, Inc.
Packager    : feedback@xxxxxxx
Summary     : Selected utilities
Description :
Selected utilities compiled from Rik Faith's huge utility collection:
agetty arch banner cal clock col colcrt colrm column ctrlaltdel dmesg
fdformat fdisk  flushb frag fsck  hex hexdump ipcrm ipcs kbdrate kill
logger look mesg mkfs.minix mkswap  more mount newgrp passwd pwd rdev
renice reset rev script setfdprm  setserial setsid setterm simpleinit
sln strings swapoff swapon syslogd tsort tunelp ul umount update wall
whereis write

    Rik Faith <faith@xxxxxxxxxx>
    Andries Brouwer <Andries.Brouwer@xxxxxx>
    Eric S. Raymond <esr@xxxxxxxxxxxxxxxxx>

SuSE series: a
ppc:~ #

so it looks like Andries Brouwer based

> do you see something like this on powerpc?...
> 10:11 nathans@troppo ~/src/util-linux-2.10q/mount 49> sudo mkfs -t minix 
> /dev/hdb9
> 21856 inodes
> 65535 blocks
> Firstdatazone=696 (696)
> Zonesize=1024
> Maxsize=268966912

> 10:12 nathans@troppo ~/src/util-linux-2.10q/mount 50> sudo od -j 1024 -x -N 
> 32 /dev/hdb9
> 0002000 5560 ffff 0003 0008 02b8 0000 1c00 1008
> 0002020 138f 0001 0000 0000 0000 0000 0000 0000
>         ^^^^
> 0002040
> 10:12 nathans@troppo ~/src/util-linux-2.10q/mount 51> 

> the 0x138f is the minix magic number which the mount "probe"
> code is looking for.

ppc:~ # mkfs -t minix /dev/hda9
21856 inodes
65535 blocks
Firstdatazone=696 (696)

ppc:~ # od -j 1024 -x -N 32 /dev/hda9
0002000 5560 ffff 0003 0008 02b8 0000 1008 1c00
0002020 138f 0001 0000 0000 0000 0000 0000 0000
ppc:~ #

so - yes it is there

> hmmm .... i think this is going to be an endian problem in
> mount.  in particular this mount_guess_fstype.c code looks
> suspect:

>     else if (minixmagic(sb.ms) == MINIX_SUPER_MAGIC
>              || minixmagic(sb.ms) == MINIX_SUPER_MAGIC2)
>          type = "minix";

> especially compared to the ext2 code immediately above it
> (this same code is in cmd/xfs/mkfs/mountinfo.c).

so you think this is a problem of the basic mount code which the xfs
utils have taken over too ... if this is the case i may look into
the SuSE mount patches if there are any and check out what they
did to make it work for mount


technical director                                       innominate AG
clustering & security                             the linux architects
tel: +49-30-308806-13   fax: -77             http://www.innominate.com

<Prev in Thread] Current Thread [Next in Thread>