Snapshot against 2.6.1 released.

Snapshot against 2.6.1 released.

[Nikita Danilov]

Hello,

new snapshot against 2.6.1 kernel is at

http://namesys.com/snapshots/2004.01.19/

look into READ.ME file for details.

Nikita.

Re: Snapshot against 2.6.1 released [someone has a patch against -mm4 ?]

[Fuzzy]

Is there any chance that namesys will also provide a patch against the 
-mm tree ? Or even better: is there already a timeline for integration 
of reiser4 in -mm ?
I usually fix the - usually minor - rejects by hand at each new release 
but if testing could be made a bit easier, that would be really nice...  ;-)

Best regards,

Vince

Nikita Danilov wrote:
> Hello,
> 
> new snapshot against 2.6.1 kernel is at
> 
> http://namesys.com/snapshots/2004.01.19/
> 
> look into READ.ME file for details.
> 
> Nikita.

Re: Snapshot against 2.6.1 released [someone has a patch against -mm4 ?]

[Mike Fedyk]

On Mon, Jan 19, 2004 at 04:36:34PM +0100, Fuzzy wrote:
> Is there any chance that namesys will also provide a patch against the 
> -mm tree ? Or even better: is there already a timeline for integration 
> of reiser4 in -mm ?
> I usually fix the - usually minor - rejects by hand at each new release 
> but if testing could be made a bit easier, that would be really nice...  ;-)

Well, if I were them, I wouldn't.

Right now the -mm tree has some stuff that's just waiting for 2.7, or is in
initial testing/merging into stock 2.6.

You really should be testing against stock 2.6 with the reiser4 filesystem
so that you don't get hit by one of the (600 in 2.6.1-mm4) patches in the
-mm series.

That way, you can help spot bugs better, and reiser4 will be merged into -mm
sooner so you'll be happy. :)

Mike

Re: Snapshot against 2.6.1 released [someone has a patch against -mm4 ?]

[Fuzzy]

> On Mon, Jan 19, 2004 at 04:36:34PM +0100, Fuzzy wrote:
> 
>>Is there any chance that namesys will also provide a patch against the 
>>-mm tree ? Or even better: is there already a timeline for integration 
>>of reiser4 in -mm ?

Mike Fedyk wrote:

> Well, if I were them, I wouldn't.
> 
> Right now the -mm tree has some stuff that's just waiting for 2.7, or is in
> initial testing/merging into stock 2.6.
> 
> You really should be testing against stock 2.6 with the reiser4 filesystem
> so that you don't get hit by one of the (600 in 2.6.1-mm4) patches in the
> -mm series.
> 
> That way, you can help spot bugs better, and reiser4 will be merged into -mm
> sooner so you'll be happy. :)

I would agree with you but:

  1) the people who would run an experimental filesystem like reiser4 
are very likely to also run with the -mm kernel tree (as is my case at 
least...)
  2) from what I've read, reiser4 should be integrated in -mm before it 
can ever think about going in mainline... so why not play with it in -mm 
now ?

Vince

Re: Snapshot against 2.6.1 released [someone has a patch against -mm4 ?]

[Mike Fedyk]

On Mon, Jan 19, 2004 at 05:11:17PM +0100, Fuzzy wrote:
>  2) from what I've read, reiser4 should be integrated in -mm before it 
> can ever think about going in mainline... so why not play with it in -mm 
> now ?

Because any bug reports you give then now you don't want them chasing bugs
in the -mm tree when they don't need to (wait until it's actually there
before that happens, and the work of getting a released version out will go
faster IMHO).

Mike

Re: Snapshot against 2.6.1 released.

[Nikita Danilov]

Nikita Danilov writes:
 > Hello,
 > 
 > new snapshot against 2.6.1 kernel is at
 > 
 > http://namesys.com/snapshots/2004.01.19/
 > 
 > look into READ.ME file for details.

Please also apply last-minute-fix.diff from there: it fixes some bug
that slipped into snapshot.

last-minute-fix.diff should be applied from fs/reiser4:

$ cd /somewhere/fs/reiser4
$ patch -p1 < /somewhereelse/last-minute-fix.diff


Sorry for this.

 > 

Nikita.

Re: Snapshot against 2.6.1 released.

[Mike Fedyk]

On Mon, Jan 19, 2004 at 07:22:49PM +0300, Nikita Danilov wrote:
> last-minute-fix.diff should be applied from fs/reiser4:

Took a look at the patch, and noticed you guys are using assert().

I'm sure you're going to have to rename that before it will be integrated
upstream, so you might as well start before then...

Mike

Re: Snapshot against 2.6.1 released.

[Domenico Andreoli]

Nikita Danilov wrote:
> Nikita Danilov writes:
>  > Hello,
>  > 
>  > new snapshot against 2.6.1 kernel is at
>  > 
>  > http://namesys.com/snapshots/2004.01.19/
>  > 
>  > look into READ.ME file for details.
> 
> Please also apply last-minute-fix.diff from there: it fixes some bug
> that slipped into snapshot.
> 
> last-minute-fix.diff should be applied from fs/reiser4:
> 
> $ cd /somewhere/fs/reiser4
> $ patch -p1 < /somewhereelse/last-minute-fix.diff
> 
> 

ehm.. my existing reiser4 partition is not mountable now that i recompiled 
2.6.1 using latest snapshot. it did not contain anything so i formatted 
it, but nothing new happened.

# mkfs.reiser4 /dev/hdc6
mkfs.reiser4 0.4.20
Copyright (C) 2001, 2002, 2003 by Hans Reiser, licensing governed by 
reiser4progs/COPYING.

Block size 4096 will be used. 

Linux 2.6.1-reiser4 is detected. 

Uuid 81a2b014-f272-4f6e-adad-e323c0cb10eb will be used. 

Reiser4 is going to be created on /dev/hdc6. 

(Yes/No): yes
Creating reiser4 on /dev/hdc6...done
# mount /dev/hdc6 /mnt/extra2
mount: you must specify the filesystem type
# mount /dev/hdc6 /mnt/extra2 -t reiser4
mount: wrong fs type, bad option, bad superblock on /dev/hdc6,
        or too many mounted file systems
#


-----[ Domenico Andreoli, aka cavok
  --[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc
    ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50

Re: Snapshot against 2.6.1 released.

[Nikita Danilov]

Domenico Andreoli writes:
 > Nikita Danilov wrote:
 > > Nikita Danilov writes:
 > >  > Hello,
 > >  > 
 > >  > new snapshot against 2.6.1 kernel is at
 > >  > 
 > >  > http://namesys.com/snapshots/2004.01.19/
 > >  > 
 > >  > look into READ.ME file for details.
 > > 
 > > Please also apply last-minute-fix.diff from there: it fixes some bug
 > > that slipped into snapshot.
 > > 
 > > last-minute-fix.diff should be applied from fs/reiser4:
 > > 
 > > $ cd /somewhere/fs/reiser4
 > > $ patch -p1 < /somewhereelse/last-minute-fix.diff
 > > 
 > > 
 > 
 > ehm.. my existing reiser4 partition is not mountable now that i recompiled 
 > 2.6.1 using latest snapshot. it did not contain anything so i formatted 
 > it, but nothing new happened.
 > 
 > # mkfs.reiser4 /dev/hdc6

Is this mkfs.reiser4 from the 2004.01.19 snapshot?

 > mkfs.reiser4 0.4.20
 > Copyright (C) 2001, 2002, 2003 by Hans Reiser, licensing governed by 
 > reiser4progs/COPYING.
 > 
 > Block size 4096 will be used. 
 > 
 > Linux 2.6.1-reiser4 is detected. 
 > 
 > Uuid 81a2b014-f272-4f6e-adad-e323c0cb10eb will be used. 
 > 
 > Reiser4 is going to be created on /dev/hdc6. 
 > 
 > (Yes/No): yes
 > Creating reiser4 on /dev/hdc6...done
 > # mount /dev/hdc6 /mnt/extra2
 > mount: you must specify the filesystem type
 > # mount /dev/hdc6 /mnt/extra2 -t reiser4
 > mount: wrong fs type, bad option, bad superblock on /dev/hdc6,
 >         or too many mounted file systems
 > #

What is in the kernel logs (dmesg, /var/log/messages)?

 > 
 > 

Nikita.

Re: Snapshot against 2.6.1 released.

[Redeeman]

the love kernel patch provides reiser4


On Mon, 2004-01-19 at 15:39, Nikita Danilov wrote:
> Hello,
> 
> new snapshot against 2.6.1 kernel is at
> 
> http://namesys.com/snapshots/2004.01.19/
> 
> look into READ.ME file for details.
> 
> Nikita.
-- 
Regards, Redeeman
()  ascii ribbon campaign - against html e-mail 
/\                        - against microsoft attachments

Re: Snapshot against 2.6.1 released.

[Mike Fedyk]

On Tue, Jan 20, 2004 at 12:47:20AM +0100, Redeeman wrote:
> the love kernel patch provides reiser4

What else does this unknown patch do?

Re: Snapshot against 2.6.1 released.

[Paolo Correnti]

I have the same "Domenico's problem":
 - downloaded Kernel 2.6.1
 - applied SNAPSHOT 2004.01.19 FIXED
 
Trying to mount Reiser4 partition all I obtain is:

Wrong Master Super Block Magic
fs/reiser4/init_siper.c line 166

Going back to Kernel 2.6.0 + SNAPSHOT 2003.12.23
I've no problems mounting and dismounting my Reiser4
partition (only kernel panic during shutdown if I
try to use another Reiser4 partition, I think is a
dismount problem)

I've also no problem with Kernel 2.6.1 + SNAPSHOT
2003.12.23 using only one Reiser4 partition (with more
partitions see the note above).

All the best

PC


--- Nikita Danilov <Nikita@Namesys.COM> wrote:
> Domenico Andreoli writes:
>  > Nikita Danilov wrote:
>  > > Nikita Danilov writes:
>  > >  > Hello,
>  > >  > 
>  > >  > new snapshot against 2.6.1 kernel is at
>  > >  > 
>  > >  > http://namesys.com/snapshots/2004.01.19/
>  > >  > 
>  > >  > look into READ.ME file for details.
>  > > 
>  > > Please also apply last-minute-fix.diff from
> there: it fixes some bug
>  > > that slipped into snapshot.
>  > > 
>  > > last-minute-fix.diff should be applied from
> fs/reiser4:
>  > > 
>  > > $ cd /somewhere/fs/reiser4
>  > > $ patch -p1 <
> /somewhereelse/last-minute-fix.diff
>  > > 
>  > > 
>  > 
>  > ehm.. my existing reiser4 partition is not
> mountable now that i recompiled 
>  > 2.6.1 using latest snapshot. it did not contain
> anything so i formatted 
>  > it, but nothing new happened.
>  > 
>  > # mkfs.reiser4 /dev/hdc6
> 
> Is this mkfs.reiser4 from the 2004.01.19 snapshot?
> 
>  > mkfs.reiser4 0.4.20
>  > Copyright (C) 2001, 2002, 2003 by Hans Reiser,
> licensing governed by 
>  > reiser4progs/COPYING.
>  > 
>  > Block size 4096 will be used. 
>  > 
>  > Linux 2.6.1-reiser4 is detected. 
>  > 
>  > Uuid 81a2b014-f272-4f6e-adad-e323c0cb10eb will be
> used. 
>  > 
>  > Reiser4 is going to be created on /dev/hdc6. 
>  > 
>  > (Yes/No): yes
>  > Creating reiser4 on /dev/hdc6...done
>  > # mount /dev/hdc6 /mnt/extra2
>  > mount: you must specify the filesystem type
>  > # mount /dev/hdc6 /mnt/extra2 -t reiser4
>  > mount: wrong fs type, bad option, bad superblock
> on /dev/hdc6,
>  >         or too many mounted file systems
>  > #
> 
> What is in the kernel logs (dmesg,
> /var/log/messages)?
> 
>  > 
>  > 
> 
> Nikita.


__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

Re: Snapshot against 2.6.1 released.

[Nikita Danilov]

Paolo Correnti writes:
 > I have the same "Domenico's problem":
 >  - downloaded Kernel 2.6.1
 >  - applied SNAPSHOT 2004.01.19 FIXED
 >  
 > Trying to mount Reiser4 partition all I obtain is:
 > 
 > Wrong Master Super Block Magic
 > fs/reiser4/init_siper.c line 166

My apology for everyone for missing this bit in the READ.ME:

you have to re-create your file-systems with mkfs supplied with this
snapshot.

 > 
 > Going back to Kernel 2.6.0 + SNAPSHOT 2003.12.23
 > I've no problems mounting and dismounting my Reiser4
 > partition (only kernel panic during shutdown if I
 > try to use another Reiser4 partition, I think is a
 > dismount problem)
 > 
 > I've also no problem with Kernel 2.6.1 + SNAPSHOT
 > 2003.12.23 using only one Reiser4 partition (with more
 > partitions see the note above).
 > 
 > All the best
 > 
 > PC
 > 

Nikita.

 > 

Re: Snapshot against 2.6.1 released.

[Paolo Correnti]

I'm sorry, I've read later Nikita message (Re:
linux-2.6.0 + reiser4 oops) telling
that Reiser4 partition has to be rebuilded.

Now I've back my Reiser4 partition with no more mount
problem.

All the best
PC

P.S. Of course, pay attention to have always a "backup
partition" to be able to copy all your Reiser4 data
before testing new snapshots.


--- Paolo Correnti <paolunix@yahoo.com> wrote:
> I have the same "Domenico's problem":
>  - downloaded Kernel 2.6.1
>  - applied SNAPSHOT 2004.01.19 FIXED
>  
> Trying to mount Reiser4 partition all I obtain is:
> 
> Wrong Master Super Block Magic
> fs/reiser4/init_siper.c line 166
> 
> Going back to Kernel 2.6.0 + SNAPSHOT 2003.12.23
> I've no problems mounting and dismounting my Reiser4
> partition (only kernel panic during shutdown if I
> try to use another Reiser4 partition, I think is a
> dismount problem)
> 
> I've also no problem with Kernel 2.6.1 + SNAPSHOT
> 2003.12.23 using only one Reiser4 partition (with
> more
> partitions see the note above).
> 
> All the best
> 
> PC
> 
> 
> --- Nikita Danilov <Nikita@Namesys.COM> wrote:
> > Domenico Andreoli writes:
> >  > Nikita Danilov wrote:
> >  > > Nikita Danilov writes:
> >  > >  > Hello,
> >  > >  > 
> >  > >  > new snapshot against 2.6.1 kernel is at
> >  > >  > 
> >  > >  > http://namesys.com/snapshots/2004.01.19/
> >  > >  > 
> >  > >  > look into READ.ME file for details.
> >  > > 
> >  > > Please also apply last-minute-fix.diff from
> > there: it fixes some bug
> >  > > that slipped into snapshot.
> >  > > 
> >  > > last-minute-fix.diff should be applied from
> > fs/reiser4:
> >  > > 
> >  > > $ cd /somewhere/fs/reiser4
> >  > > $ patch -p1 <
> > /somewhereelse/last-minute-fix.diff
> >  > > 
> >  > > 
> >  > 
> >  > ehm.. my existing reiser4 partition is not
> > mountable now that i recompiled 
> >  > 2.6.1 using latest snapshot. it did not contain
> > anything so i formatted 
> >  > it, but nothing new happened.
> >  > 
> >  > # mkfs.reiser4 /dev/hdc6
> > 
> > Is this mkfs.reiser4 from the 2004.01.19 snapshot?
> > 
> >  > mkfs.reiser4 0.4.20
> >  > Copyright (C) 2001, 2002, 2003 by Hans Reiser,
> > licensing governed by 
> >  > reiser4progs/COPYING.
> >  > 
> >  > Block size 4096 will be used. 
> >  > 
> >  > Linux 2.6.1-reiser4 is detected. 
> >  > 
> >  > Uuid 81a2b014-f272-4f6e-adad-e323c0cb10eb will
> be
> > used. 
> >  > 
> >  > Reiser4 is going to be created on /dev/hdc6. 
> >  > 
> >  > (Yes/No): yes
> >  > Creating reiser4 on /dev/hdc6...done
> >  > # mount /dev/hdc6 /mnt/extra2
> >  > mount: you must specify the filesystem type
> >  > # mount /dev/hdc6 /mnt/extra2 -t reiser4
> >  > mount: wrong fs type, bad option, bad
> superblock
> > on /dev/hdc6,
> >  >         or too many mounted file systems
> >  > #
> > 
> > What is in the kernel logs (dmesg,
> > /var/log/messages)?
> > 
> >  > 
> >  > 
> > 
> > Nikita.
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus"
> Sweepstakes
> http://hotjobs.sweepstakes.yahoo.com/signingbonus


__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

Re: Snapshot against 2.6.1 released.

[Frank Benkstein]

On Mon, 19 Jan 2004 16:08:48 -0800
Mike Fedyk <mfedyk@matchmail.com> wrote:

> On Tue, Jan 20, 2004 at 12:47:20AM +0100, Redeeman wrote:
> > the love kernel patch provides reiser4
> 
> What else does this unknown patch do?

Have a look here: http://forums.gentoo.org/viewtopic.php?t=125170

Re: Snapshot against 2.6.1 released.

[Redeeman]

alot.

newest version:
http://jpcox.student.iastate.edu/linux/patches/2.6/2.6.1/2.6.1-love6

On Tue, 2004-01-20 at 01:08, Mike Fedyk wrote:
> On Tue, Jan 20, 2004 at 12:47:20AM +0100, Redeeman wrote:
> > the love kernel patch provides reiser4
> 
> What else does this unknown patch do?
-- 
Regards, Redeeman
()  ascii ribbon campaign - against html e-mail 
/\                        - against microsoft attachments

Re: Snapshot against 2.6.1 released.

[Mike Fedyk]

On Tue, Jan 20, 2004 at 02:11:45AM -0800, Paolo Correnti wrote:
> P.S. Of course, pay attention to have always a "backup
> partition" to be able to copy all your Reiser4 data
> before testing new snapshots.

Right, and keep a copy of the data from *before* you copied the data on that
non-reiser4 partition.

If you have another empty filesystem around for scratch data, you can use
reiser4 for that, but not for data you care about.

Re: Snapshot against 2.6.1 released.

[Vince]

Nikita Danilov wrote:
> Paolo Correnti writes:
>  > I have the same "Domenico's problem":
>  >  - downloaded Kernel 2.6.1
>  >  - applied SNAPSHOT 2004.01.19 FIXED
>  >  
>  > Trying to mount Reiser4 partition all I obtain is:
>  > 
>  > Wrong Master Super Block Magic
>  > fs/reiser4/init_siper.c line 166
> 
> My apology for everyone for missing this bit in the READ.ME:
> 
> you have to re-create your file-systems with mkfs supplied with this
> snapshot.
> 

Is it really mandatory to re-create or will a "fsck.reiser4 --build-fs" 
be able to fix the filesystem to the new format ? (the data on my 
reiser4 partition is not important at all, but i'd like to avoid erase 
it if possible).

By the way, a small complaint: it would be nice to update the version 
numbers the next time there are changes, as e.g. for libaal-0.4.15, a 
diffstat with libaal-0.4.15 from the previous snapshot gives something like:

[...]
  src/bitops.c            |    2
  src/block.c             |    2
  src/debug.c             |    2
  src/device.c            |   12 -
  src/exception.c         |    2
  src/file.c              |    2
  src/gauge.c             |    2
  src/hash.c              |    2
  src/libaal.c            |    4
  src/list.c              |    2
  src/malloc.c            |    2
  src/print.c             |    2
  src/stream.c            |    2
  src/string.c            |   21 --
  src/ui.c                |    2

And the diff for reiser4progs-0.4.20 looks huge...  8-o

Vince

Re: Snapshot against 2.6.1 released.

[Vince]

[-- Attachment #1: Type: text/plain, Size: 2832 bytes --]


> Nikita Danilov wrote:

>> My apology for everyone for missing this bit in the READ.ME:
>>
>> you have to re-create your file-systems with mkfs supplied with this
>> snapshot.
>>

I wrote:
> Is it really mandatory to re-create or will a "fsck.reiser4 --build-fs" 
> be able to fix the filesystem to the new format ? 
> 

(replying to myself) It seems indeed really mandatory... I got a kernel 
oops while fsck-ing my old reiser4 partition with the new 
kernel+userspace snapshot (kernel is 2.6.2-rc1-mm1, reiser4 snapshot is 
2004.01.19.fixed). And now the (unfixed/corrupted) partition causes the 
following oops when I try to mount it:

reiser4[mount(177)]: get_ready_format40 
(fs/reiser4/plugin/disk_format/disk_format40.c:248)[nikita-3228]:
WARNING: Key format mismatch. Only large keys are supported.
Unable to handle kernel NULL pointer dereference at virtual address 00000000
  printing eip:
c01b762d
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
CPU:    0
EIP:    0060:[<c01b762d>]    Not tainted VLI
EFLAGS: 00010246
EIP is at unhash_unformatted_node_nolock+0x1d/0x70
eax: 00000000   ebx: decea7c0   ecx: 00000000   edx: 00000000
esi: dfde6000   edi: 00000000   ebp: c14d0418   esp: dfde7c38
ds: 007b   es: 007b   ss: 0068
Process mount (pid: 177, threadinfo=dfde6000 task=dfdfe6b0)
Stack: dfde6000 dfde6000 c01b769d decea7c0 decea7c0 c01d9437 decea7c0 
decea7c0
        00000000 00000000 00000000 00000000 00000000 00000000 00000000 
00000000
        00000000 00000000 00000000 00000000 00000000 00000000 00000000 
00000000
Call Trace:
  [<c01b769d>] unhash_unformatted_jnode+0x1d/0x40
  [<c01d9437>] reiser4_invalidatepage+0xd7/0x160
  [<c0143ba7>] do_invalidatepage+0x27/0x30
  [<c0143c2b>] truncate_complete_page+0x7b/0x80
  [<c0143e00>] truncate_inode_pages+0x100/0x3c0
  [<c01704ef>] wake_up_inode+0xf/0x30
  [<c01769bb>] write_inode_now+0x4b/0x90
  [<c017000b>] generic_forget_inode+0x14b/0x180
  [<c01700c2>] iput+0x62/0x80
  [<c01cf6b9>] done_formatted_fake+0x59/0x80
  [<c01ddabe>] done_super+0x1e/0x30
  [<c01ddb3a>] reiser4_fill_super+0x6a/0x70
  [<c015d314>] get_sb_bdev+0x124/0x160
  [<c01d712f>] reiser4_get_sb+0x2f/0x40
  [<c01ddad0>] reiser4_fill_super+0x0/0x70
  [<c015d57f>] do_kern_mount+0x5f/0xe0
  [<c0172e08>] do_add_mount+0x78/0x150
  [<c01730f4>] do_mount+0x124/0x170
  [<c0172f60>] copy_mount_options+0x80/0xf0
  [<c01734af>] sys_mount+0xbf/0x140
  [<c02f5ebe>] sysenter_past_esp+0x43/0x65

Code: e9 69 fe ff ff 89 f6 8d bc 27 00 00 00 00 53 83 ec 04 8b 5c 24 0c 
8b 4b 28 8b 53 14 03 53 0c 8b 41 40 48 21 c2 8b 41 3c 8d 0c 90 <8b> 01 
85 c0 74 14 8d 50 1c 0f 18 02 90 39 d8 74 32 8b 40 1c 89
  <6>note: mount[177] exited with preempt_count 2

I also attach the output of debugfs.reiser4 -t in case it could help 
(this is still a bug that mounting a corrupted partition can cause a 
kernel oops)...

[-- Attachment #2: debugfs.log --]
[-- Type: text/plain, Size: 2286 bytes --]

NODE (22) LEVEL=2 ITEMS=2 SPACE=3976 MKFS ID=0x32cfc610 FLUSH=0x0
#0  NPTR (nodeptr40): [29:1(SD):0:2a:0] OFF 28, LEN=8, flags=0x0 UNITS=1
[23]
------------------------------------------------------------------------------
#1  NPTR (nodeptr40): [2a:4(FB):74657374000000:10000:e50] OFF 36, LEN=8, flags=0x0 UNITS=1
[26]
==============================================================================
NODE (23) LEVEL=1 ITEMS=4 SPACE=0 MKFS ID=0x32cfc610 FLUSH=0x0
#0  SD (stat40): [29:1(SD):0:2a:0] OFF 28, LEN=44, flags=0x0 UNITS=1
exts:		2
mask:		0x3
plugin:		sdext_lw
offset:		2
len:		14
mode:		drwxr-xr-x
nlink:		3
size:		3
plugin:		sdext_unix
offset:		16
len:		28
uid:		0
gid:		0
atime:		Sun Jan 18 23:08:41 2004
mtime:		Sun Jan 18 23:09:34 2004
ctime:		Sun Jan 18 23:09:34 2004
rdev:		150
bytes:		150
------------------------------------------------------------------------------
#1  DENTRY (cde40): [2a:0(NAME):0:0:0] OFF 72, LEN=152, flags=0x0 UNITS=3
NR  NAME              OFFSET HASH                              SDKEY             
  0 .                     80 0000000000000000:0000000000000000 0000291:000002a
  1 ..                   104 0000000000000000:0000000000000000 0000291:000002a
  2 test                 128 0000000000000000:0000000000000000 00002a1:0010000
------------------------------------------------------------------------------
#2  SD (stat40): [2a:1(SD):74657374000000:10000:0] OFF 224, LEN=56, flags=0x0 UNITS=1
exts:		3
mask:		0x7
plugin:		sdext_lw
offset:		2
len:		14
mode:		-rw-r--r--
nlink:		1
size:		6120
plugin:		sdext_unix
offset:		16
len:		28
uid:		0
gid:		0
atime:		Sun Jan 18 23:09:34 2004
mtime:		Sun Jan 18 23:10:35 2004
ctime:		Sun Jan 18 23:10:35 2004
rdev:		12240
bytes:		12240
plugin:		sdext_lt
offset:		44
len:		12
atime:		461999488
mtime:		253757736
ctime:		253757736
------------------------------------------------------------------------------
#3  TAIL (tail40): [2a:4(FB):74657374000000:10000:0] OFF 280, LEN=3664, flags=0x0 
==============================================================================
NODE (26) LEVEL=1 ITEMS=1 SPACE=1574 MKFS ID=0x32cfc610 FLUSH=0x0
#0  TAIL (tail40): [2a:4(FB):74657374000000:10000:e50] OFF 28, LEN=2456, flags=0x0 
==============================================================================

Re: Snapshot against 2.6.1 released.

[Nikita Danilov]

Vince writes:
 > 
 > > Nikita Danilov wrote:
 > 
 > >> My apology for everyone for missing this bit in the READ.ME:
 > >>
 > >> you have to re-create your file-systems with mkfs supplied with this
 > >> snapshot.
 > >>
 > 
 > I wrote:
 > > Is it really mandatory to re-create or will a "fsck.reiser4 --build-fs" 
 > > be able to fix the filesystem to the new format ? 
 > > 
 > 
 > (replying to myself) It seems indeed really mandatory... I got a kernel 
 > oops while fsck-ing my old reiser4 partition with the new 
 > kernel+userspace snapshot (kernel is 2.6.2-rc1-mm1, reiser4 snapshot is 
 > 2004.01.19.fixed). And now the (unfixed/corrupted) partition causes the 
 > following oops when I try to mount it:

Yes, mount was unable to handle an error. This is hopefully fixed and
will be included into new snapshot.


 > 
 > reiser4[mount(177)]: get_ready_format40 
 > (fs/reiser4/plugin/disk_format/disk_format40.c:248)[nikita-3228]:
 > WARNING: Key format mismatch. Only large keys are supported.

Nikita.

Re: Snapshot against 2.6.1 released.

[Mike Fedyk]

On Thu, Jan 22, 2004 at 08:20:17PM +0300, Nikita Danilov wrote:
> Yes, mount was unable to handle an error. This is hopefully fixed and
> will be included into new snapshot.

Vince,

Keep a compressed image of that filesystem so that you can restore it and
remount to see if the oops is fixed in future snapshots.

Mike