All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Michael James <Michael.James@csiro.au>
Cc: reiserfs-list@namesys.com
Subject: Re: Trouble with Suse9.3's reiser4
Date: Tue, 16 Aug 2005 22:52:55 -0700	[thread overview]
Message-ID: <4302D0B7.4060900@namesys.com> (raw)
In-Reply-To: <200508171445.46519.Michael.James@csiro.au>

Michael James wrote:

>Dear Reiser experts and enthusiasts,
>
>I can't get the reiser4 in Suse9.3 Pro to work.
>
>The problem is completely repeatable, happens every time.
>
>Unmount a happy reiserfs3.6 data partition.
>Re-format it as reiser4.
>Re-mount it.
>Copy something BIG into it.
>As soon as it sees a file >2 Gig, the copy process hangs.
>Once the copy is hung anything that reads that partition hangs too.
>
>
>The system is a Dell 1655MC blade server.
>It's a fully patched Suse9.3 pro machine.
>All the reiser components are stock Suse.
>
>a3:~ # cat /etc/SuSE-release
>SuSE Linux 9.3 (i586)
>VERSION = 9.3
>
>a3:~ # cat /proc/version
>Linux version 2.6.11.4-21.8-bigsmp (geeko@buildhost) (gcc version 3.3.5 
>20050117 (prerelease) (SUSE Linux)) #1 SMP Tue Jul 19 12:42:37 UTC 2005
>
>a3:~ # l /boot/vmlinuz-2.6.11.4-21.8-bigsmp
>-rw-r--r--  1 root root 1555967 Jul 24
>	 00:55 /boot/vmlinuz-2.6.11.4-21.8-bigsmp
>
>
>Here's the simple path to destruction:
>
>Have a lot of fun...
>a3:~ # umount /coda
>
>a3:~ # mkfs.reiser4 /dev/sda4
>mkfs.reiser4 1.0.3
>Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser,
> licensing governed by reiser4progs/COPYING.
>
>Block size 4096 will be used.
>Linux 2.6.11.4-21.8-bigsmp is detected.
>Uuid 01d3e4b0-e5b2-4b1b-a525-17fd4c239af1 will be used.
>Reiser4 is going to be created on /dev/sda4.
>(Yes/No): Yes
>Creating reiser4 on /dev/sda4 ... done
>
>a3:~ # fsck.reiser4  /dev/sda4
>
>*******************************************************************
>This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
>*******************************************************************
>
>Fscking the /dev/sda4 block device.
>Will check the consistency of the Reiser4 SuperBlock.
>Will check the consistency of the Reiser4 FileSystem.
>Continue?
>(Yes/No): Yes
>***** fsck.reiser4 started at Wed Aug 17 11:46:19 2005
>Reiser4 fs was detected on /dev/sda4.
>Master super block (16):
>magic:          ReIsEr4
>blksize:        4096
>format:         0x0 (format40)
>uuid:           01d3e4b0-e5b2-4b1b-a525-17fd4c239af1
>label:          <none>
>
>Format super block (17):
>plugin:         format40
>description:    Disk-format for reiser4.
>magic:          ReIsEr40FoRmAt
>flushes:        0
>mkfs id:        0x2783ddb9
>blocks:         7349737
>free blocks:    7349476
>root block:     23
>tail policy:    0x2 (smart)
>next oid:       0x10000
>file count:     0
>tree height:    2
>key policy:     LARGE
>
>
>CHECKING STORAGE TREE
>        Read nodes 2
>        Nodes left in the tree 2
>                Leaves of them 1, Twigs of them 1
>        Time interval: Wed Aug 17 11:46:21 2005 - Wed Aug 17 11:46:21 
>2005
>CHECKING EXTENT REGIONS.
>        Read twigs 1
>        Time interval: Wed Aug 17 11:46:21 2005 - Wed Aug 17 11:46:21 
>2005
>CHECKING SEMANTIC TREE
>        Found 1 objects.
>        Time interval: Wed Aug 17 11:46:21 2005 - Wed Aug 17 11:46:21 
>2005
>***** fsck.reiser4 finished at Wed Aug 17 11:46:21 2005
>Closing fs...done
>
>FS is consistent.
>
>a3:~ # mount -t reiser4 /dev/sda4 /coda
>
>a3:~ # mkdir /coda/blastN
>a3:~ # mkdir /coda/blastP
>
>a3:~ # chown -R biofile:www /coda/
>a3:~ # su - biofile
>
>biofile@a3:~ $  pwd
>/home/cbf/biofile
>
>
>biofile@a3:~ $  cp -av  db/blastN/  /coda/blastN/
>`db/blastN/' -> `/coda/blastN/blastN'
>`db/blastN/nt' -> `/coda/blastN/blastN/nt'
>`db/blastN/nt/.nt.log' -> `/coda/blastN/blastN/nt/.nt.log'
>`db/blastN/nt/nt.00.nhr' -> `/coda/blastN/blastN/nt/nt.00.nhr'
>
>And there it hangs,  ^C does no good.
>Close that local window,  log in again and:
>
>
>Have a lot of fun...
>a3:~ # df
>Filesystem           1K-blocks      Used Available Use% Mounted on
>/dev/sda2              4080316   2583200   1497116  64% /
>tmpfs                  1035968         0   1035968   0% /dev/shm
>/dev/sda1                23300      8395     13702  38% /boot
>darius:/home         714091552 491106336 222985216  69% /home
>darius:/var/spool/share
>                      20136800   3830208  16306592  20% /var/spool/share
>/dev/sda4             27934744    519076  27415668   2% /coda
>
>
>a3:/var/log # ls -la /coda/
>
>And that's it for that window too, it's hung beyond ^C retrieving it.
>
>This is what always happens,
> I think it relates to the files being bigger than 2 Gig.
>This time it died copying nt.nhr
>
>ls -la  /home/cbf/biofile/db/blastN/nt/nt.00.nhr
>-rw-r--r--   1 biofile www 179427600 2005-08-05 20:31 nt.00.nhr
>
>Performance on the filesystem is important,
> I'm keen to get reiser4 working.
>Any help with this would be appreciated,
> if there's any extra info needed, just ask,
>
>michaelj
>
>  
>
Try an official Linus kernel with our latest snapshot....

Hans

      reply	other threads:[~2005-08-17  5:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17  4:45 Trouble with Suse9.3's reiser4 Michael James
2005-08-17  5:52 ` Hans Reiser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4302D0B7.4060900@namesys.com \
    --to=reiser@namesys.com \
    --cc=Michael.James@csiro.au \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.