From: Yury Umanets <umka@namesys.com>
To: Ian Wienand <ianw@gelato.unsw.edu.au>
Cc: Oleg Drokin <green@namesys.com>,
reiserfs-dev@namesys.com, reiserfs-list@namesys.com,
linux-kernel@vger.kernel.org
Subject: Re: reiser4 snapshot for August 26th.
Date: Wed, 27 Aug 2003 10:03:31 +0400 [thread overview]
Message-ID: <1061964211.15513.41.camel@haron.namesys.com> (raw)
In-Reply-To: <20030827055204.GA18114@cse.unsw.EDU.AU>
On Wed, 2003-08-27 at 09:52, Ian Wienand wrote:
> On Tue, Aug 26, 2003 at 02:22:33PM +0400, Oleg Drokin wrote:
> > Fixed some bugs. And finally reiser4 should compile on 64bit boxes
> > (hm. somebody try it, as I am unable to build any 2.6 kernel for
> > ia64).
>
> I built this with IA64 2.6.0-test4, it works but there were lots of
> warnings (I can put up a log if you want it). This was on a dual
> processor Itanium 2 box.
>
> First up, I tried a little test to make a few files, but once I had
> unmounted the disk I couldn't re-mount it.
>
> --- example testing below ---
> bash-2.05b# mkfs.reiser4 /dev/sda5
> mkfs.reiser4 0.4.12
> Copyright (C) 2001, 2002, 2003 by Hans Reiser, licensing governed by reiser4progs/COPYING.
>
> Information: Reiser4 is going to be created on /dev/sda5.
> (Yes/No): Yes
> Creating reiser4 on /dev/sda5...
> mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f7661
> mkfs.reiser4(5676): unaligned access to 0x60000000000242fa, ip=0x20000000000f77a1
> mkfs.reiser4(5676): unaligned access to 0x6000000000024302, ip=0x20000000000f78e1
> mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f2671
> done
> Synchronizing /dev/sda5...done
I will fix it soon.
Thanks for report.
Regards.
next prev parent reply other threads:[~2003-08-27 6:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 10:22 reiser4 snapshot for August 26th Oleg Drokin
2003-08-26 18:20 ` Steven Cole
2003-08-26 18:26 ` Alex Zarochentsev
2003-08-26 19:36 ` Felipe Alfaro Solana
2003-08-26 19:43 ` Oleg Drokin
2003-08-26 19:51 ` Steven Cole
2003-08-26 20:05 ` Mike Fedyk
2003-08-26 20:13 ` Steven Cole
2003-08-26 20:26 ` Mike Fedyk
2003-08-26 20:25 ` Steven Cole
2003-08-26 20:30 ` Hans Reiser
2003-08-26 20:28 ` Hans Reiser
2003-08-26 19:53 ` Mike Fedyk
2003-08-26 19:57 ` how to log reiser and raid0 crash? 2.6.0-t4 Resident Boxholder
2003-08-26 22:20 ` Resident Boxholder
2003-08-27 10:35 ` Oleg Drokin
2003-08-28 7:28 ` Resident Boxholder
2003-08-26 18:38 ` reiser4 snapshot for August 26th Steven Cole
2003-08-26 19:22 ` Hans Reiser
2003-08-26 18:38 ` Oleg Drokin
2003-08-26 18:41 ` Hans Reiser
2003-08-26 18:41 ` Alex Zarochentsev
2003-08-26 19:14 ` Steven Cole
2003-08-28 11:46 ` Alex Zarochentsev
2003-08-28 15:12 ` Steven Cole
2003-08-28 16:33 ` Tupshin Harper
2003-08-26 19:15 ` Hans Reiser
2003-08-28 18:31 ` Vladimir Demidov
2003-08-26 21:28 ` Diego Calleja García
2003-08-27 7:38 ` Oleg Drokin
2003-08-27 5:52 ` Ian Wienand
2003-08-27 6:03 ` Yury Umanets [this message]
2003-08-27 11:19 ` Felipe Alfaro Solana
2003-08-27 15:54 ` Hans Reiser
2003-09-15 11:15 ` reiser4 snapshot 20030905 [OOPS] Maciej Soltysiak
2003-09-15 13:52 ` Nikita Danilov
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=1061964211.15513.41.camel@haron.namesys.com \
--to=umka@namesys.com \
--cc=green@namesys.com \
--cc=ianw@gelato.unsw.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox