From: Isaac Chanin <chanin@WPI.EDU>
To: reiserfs-list@namesys.com
Subject: AMD64/Reiser4 testing and problems
Date: Thu, 02 Dec 2004 18:13:39 -0500 [thread overview]
Message-ID: <41AFA1A3.1040509@wpi.edu> (raw)
Hi,
I did some testing with Resier4 on AMD and was wondering if perhaps
debug information or anything on this could help with getting Resier4
stable and working on AMD64.
I have read that if AMD would give an AMD64 cpu that would be a big
help, but it doesn't seem inheriantly impossible to fix the problem from
error reports and such.
Anyways, here are the results for my testing. I used a mm 2.6.10-rc2
kernel and the filesystem was in a file mounted by loopback.
http://users.wpi.edu/~chanin/r4log.txt
The commands I tried were as follows:
(r4 was a 512mb file made by dd)
mount -o loop /root/r4 /root/r4dir (worked)
df -h (worked)
cd /root/r4 (worked)
ls (worked)
ls -la (worked)
mkdir linux (worked)
cp -r /usr/src/linux linux (worked, but the program hung at the end,
kill -9 had no effect)
ls (worked, but the program hung at the end, kill -9 had no effect)
cd /root/r4 (no output, program crashed immediately)
Thanks for taking the time to read over the problems - and if there's
anymore testing I could do or whatnot just ask; and, thanks for making
what will (hopefully) soon be the fastest file system to work on my
computer!
next reply other threads:[~2004-12-02 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 23:13 Isaac Chanin [this message]
2004-12-04 21:27 ` AMD64/Reiser4 testing and problems Alex Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 8:04 Isaac Chanin
2004-12-21 5:46 Isaac Chanin
2004-12-22 5:45 ` Isaac Chanin
2005-01-01 21:49 Recursive modfied-timestamp? Hans Reiser
2005-01-02 4:22 ` AMD64/Reiser4 testing and problems Isaac Chanin
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=41AFA1A3.1040509@wpi.edu \
--to=chanin@wpi.edu \
--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.