| View previous topic :: View next topic |
| Author |
Message |
Angry Geek
Apprentice
Joined: 23 Apr 2003
Posts: 162
Location: .uk
|
 Posted: Fri Sep 30, 2005 9:32 pm Post subject: Reiser4 Question |
 |
|
Quick question about Reiser4
"Reiser4 is a distinct filesystem type from reiserfs (V3). It's therefore not possible to use reiserfs file systems with reiser4."
Does this actaully mean I cannot have a ReiserFS partiton alongside a Reiser4 Partiton? Say /home - Reiser4 but / - ReiserFS? So one or the other?
Cheers.
_________________
Linux user 327411. Go get counted! |
|
| Back to top |
|
 |
codergeek42
Bodhisattva
Joined: 05 Apr 2004
Posts: 5142
Location: Anaheim, CA (USA)
|
| Posted: Fri Sep 30, 2005 9:50 pm Post subject: |
|
|
My understanding of it is that you can have different filesystems (such as ReiserFS v4 and v3.6) on separate partitions. This is saying that the on-disk formats of the two ReiserFS incarnations are not compatible, so you cannot "upgrade" from v3 to v4.
_________________
~~ Peter: Programmer, Mathematician, STEM & Free Software Advocate, Enlightened Agent, Transhumanist, Fedora contributor
Who am I? :: EFF & FSF |
|
| Back to top |
|
|
Angry Geek
Apprentice
Joined: 23 Apr 2003
Posts: 162
Location: .uk
|
| Posted: Sat Oct 01, 2005 6:38 pm Post subject: |
|
|
Well, I've patched vanilla-sources 2.6.13-1 with the appropriate Reiser4 patch from the namesys website.
On compile I get this.
| Code: |
CC fs/reiser4/debug.o
In file included from fs/reiser4/lock.h:15,
from fs/reiser4/context.h:14,
from fs/reiser4/debug.c:25:
fs/reiser4/txnmgr.h: In function `spin_atom_init':
fs/reiser4/txnmgr.h:512: error: duplicate case value
fs/reiser4/txnmgr.h:512: error: previously used here
fs/reiser4/txnmgr.h: In function `spin_txnh_init':
fs/reiser4/txnmgr.h:513: error: duplicate case value
fs/reiser4/txnmgr.h:513: error: previously used here
fs/reiser4/txnmgr.h: In function `spin_txnmgr_init':
fs/reiser4/txnmgr.h:514: error: duplicate case value
fs/reiser4/txnmgr.h:514: error: previously used here
In file included from fs/reiser4/context.h:14,
from fs/reiser4/debug.c:25:
fs/reiser4/lock.h: In function `spin_stack_init':
fs/reiser4/lock.h:198: error: duplicate case value
fs/reiser4/lock.h:198: error: previously used here
In file included from fs/reiser4/znode.h:16,
from fs/reiser4/tree.h:15,
from fs/reiser4/super.h:9,
from fs/reiser4/debug.c:26:
fs/reiser4/jnode.h: In function `spin_jnode_init':
fs/reiser4/jnode.h:344: error: duplicate case value
fs/reiser4/jnode.h:344: error: previously used here
fs/reiser4/jnode.h: In function `spin_jload_init':
fs/reiser4/jnode.h:348: error: duplicate case value
fs/reiser4/jnode.h:348: error: previously used here
In file included from fs/reiser4/super.h:9,
from fs/reiser4/debug.c:26:
fs/reiser4/tree.h: In function `spin_epoch_init':
fs/reiser4/tree.h:169: error: duplicate case value
fs/reiser4/tree.h:169: error: previously used here
In file included from fs/reiser4/debug.c:26:
fs/reiser4/super.h: In function `spin_super_init':
fs/reiser4/super.h:379: error: duplicate case value
fs/reiser4/super.h:379: error: previously used here
make[2]: *** [fs/reiser4/debug.o] Error 1
make[1]: *** [fs/reiser4] Error 2
make: *** [fs] Error 2
|
Any ideas?
This should really be moved into unsupported. Could a moderator move it? Sorry.
_________________
Linux user 327411. Go get counted! |
|
| Back to top |
|
|
tomk
Bodhisattva
Joined: 23 Sep 2003
Posts: 7221
Location: Sat in front of my computer
|
| Posted: Sat Oct 01, 2005 7:02 pm Post subject: |
|
|
| Angry Geek wrote: | | This should really be moved into unsupported. Could a moderator move it? Sorry. |
Moved from Kernel & Hardware to Unsupported Software.
_________________
Search | Read | Answer | Report | Strip |
|
| Back to top |
|
|
playfool
l33t
Joined: 01 Jun 2004
Posts: 688
Location: Ã
rhus, Denmark
|
| Posted: Sat Oct 01, 2005 7:06 pm Post subject: |
|
|
| eventually ConvertFS should support the ReiserFS3 to Reiser4 move, but that's in the distant future compared to getting in the vanilla kernel |
|
| Back to top |
|
|
Angry Geek
Apprentice
Joined: 23 Apr 2003
Posts: 162
Location: .uk
|
| Posted: Sat Oct 01, 2005 7:13 pm Post subject: |
|
|
Apparently this is the hotfix on IKML.org and it seems to compile fine afterwards....
_________________
Linux user 327411. Go get counted! |
|
| Back to top |
|
|
SlackwareInAZ
Tux's lil' helper
Joined: 29 Aug 2005
Posts: 92
|
| Posted: Sat Oct 01, 2005 10:14 pm Post subject: |
|
|
Angry Geek,
I had the same results when I patched 2.6.13.1 or 2.6.13.2 with the newest namesys 2.6.13 patch.
Is the link you posted to a patch and how do you use that? Cut and paste the text to a patch and then patch the kernel source after applying the namesys patch?
Any guidance would be most appreciated (Can't wait until Reiser4 is included in the vanilla kernel sources. Will that ever happen??!!)
Gary  |
|
| Back to top |
|
|
StringCheesian
l33t
Joined: 21 Oct 2003
Posts: 887
|
| Posted: Sat Oct 01, 2005 11:21 pm Post subject: |
|
|
Just a little warning.
On this howto:
http://gentoo-wiki.com/HOWTO_Reiser4_With_Gentoo-Sources
...it says: | Quote: | | On the 2.6.13 patch: From The Namesys Reiser4 README (A changelog, really): "09/01/2005 replacemenet for all reiser4 patches in 2.6.13-mm1 starting from reiser4-only.patch Changes: big cleanup of super operations NOTE: not very stable" Being that the patch itself is unstable, I doubt we'll see a vanilla 2.6.13 patch anytime soon. I'm going to continue using the 2.6.12 line, as it was stable enough and I don't want to move to a mm-series kernel to move to 2.6.13. --UberDumm (9/17/05) |
So be careful. You might want to go with 2.6.12 if the changes for 2.6.13 are really that unstable. |
|
| Back to top |
|
|
Redeeman
l33t
Joined: 25 Sep 2003
Posts: 958
Location: Portugal
|
| Posted: Sun Oct 02, 2005 6:52 am Post subject: |
|
|
| StringCheesian wrote: | Just a little warning.
On this howto:
http://gentoo-wiki.com/HOWTO_Reiser4_With_Gentoo-Sources
...it says: | Quote: | | On the 2.6.13 patch: From The Namesys Reiser4 README (A changelog, really): "09/01/2005 replacemenet for all reiser4 patches in 2.6.13-mm1 starting from reiser4-only.patch Changes: big cleanup of super operations NOTE: not very stable" Being that the patch itself is unstable, I doubt we'll see a vanilla 2.6.13 patch anytime soon. I'm going to continue using the 2.6.12 line, as it was stable enough and I don't want to move to a mm-series kernel to move to 2.6.13. --UberDumm (9/17/05) |
So be careful. You might want to go with 2.6.12 if the changes for 2.6.13 are really that unstable. |
and on that note, if you already ran your filesystem with 2.6.13, or created it with the latest reiser4progs, you can NOT go back to 2.6.12. |
|
| Back to top |
|
|
frostschutz
Advocate
Joined: 22 Feb 2005
Posts: 2977
Location: Germany
|
| Posted: Sun Oct 02, 2005 10:59 am Post subject: |
|
|
| playfool wrote: | | eventually ConvertFS should support the ReiserFS3 to Reiser4 move, but that's in the distant future compared to getting in the vanilla kernel |
If you want to use convertfs, be careful and read Bug 107635 (and other resources) first, it's not very safe to use... |
|
| Back to top |
|
|
i92guboj
Bodhisattva
Joined: 30 Nov 2004
Posts: 10315
Location: Córdoba (Spain)
|
| Posted: Sun Oct 02, 2005 10:29 pm Post subject: Re: Reiser4 Question |
|
|
| Angry Geek wrote: | Quick question about Reiser4
"Reiser4 is a distinct filesystem type from reiserfs (V3). It's therefore not possible to use reiserfs file systems with reiser4."
Does this actaully mean I cannot have a ReiserFS partiton alongside a Reiser4 Partiton? Say /home - Reiser4 but / - ReiserFS? So one or the other?
Cheers. |
No problem about that (other than the problem that reiser4 is in itself  ). What that statement means is what codergeek said above. It is possible, for example, to mount an ext3 partition like ext2 (and viceversa) but this compatibility does not exist between reiser 3.6 and reiser 4.
About seeing reiser4 in vanilla... you can wait a few years. Reiser4 is far from the standard stability required for a patch to be included into the vanilla code. Before that happens we will see, probably, reiser4 in gentoo-sources. To put and example, the fbsplash is since so long into gentoo-sources (previously gentoo-dev-sources), but is not still in vanilla. As r4 is much more unstable than fbsplash. Seeking the same golden rule it can take about 5 or 6 years to get that patch in vanilla (if ever goes into vanilla, which I highly doubt)  |
|
| Back to top |
|
|
Jake
Veteran
Joined: 31 Jul 2003
Posts: 1132
|
| Posted: Mon Oct 03, 2005 12:50 am Post subject: |
|
|
| Angry Geek wrote: | | Apparently this is the hotfix on IKML.org and it seems to compile fine afterwards.... |
Use 2.6.12 with the 3rd Namesys patch if you don't want trouble. The 1st 2.6.13 patch is a port of a version that didn't work well in -mm. It isn't well tested yet. The developers want to know if it was -mm causing the problems or recent changes in the reiser4 code required to get into vanilla.
SlackwareInAZ, if you don't know how to fix the reiser4 code with the mailing list patch, you should probably be using 2.6.12 as recommended above. |
|
| Back to top |
|
|
Jon Beilin
Tux's lil' helper
Joined: 18 Dec 2003
Posts: 90
Location: Hanover, NH
|
| Posted: Mon Oct 03, 2005 9:36 pm Post subject: Re: Reiser4 Question |
|
|
| 6thpink wrote: |
About seeing reiser4 in vanilla... you can wait a few years. Reiser4 is far from the standard stability required for a patch to be included into the vanilla code. Before that happens we will see, probably, reiser4 in gentoo-sources. To put and example, the fbsplash is since so long into gentoo-sources (previously gentoo-dev-sources), but is not still in vanilla. As r4 is much more unstable than fbsplash. Seeking the same golden rule it can take about 5 or 6 years to get that patch in vanilla (if ever goes into vanilla, which I highly doubt) |
from the lkml i got the impression the larger problem was with the plugin system as it can result in non-fs agnostic programs. |
|
| Back to top |
|
|
Jake
Veteran
Joined: 31 Jul 2003
Posts: 1132
|
| Posted: Mon Oct 03, 2005 11:44 pm Post subject: Re: Reiser4 Question |
|
|
| Jon Beilin wrote: | | 6thpink wrote: |
About seeing reiser4 in vanilla... you can wait a few years. Reiser4 is far from the standard stability required for a patch to be included into the vanilla code. Before that happens we will see, probably, reiser4 in gentoo-sources. To put and example, the fbsplash is since so long into gentoo-sources (previously gentoo-dev-sources), but is not still in vanilla. As r4 is much more unstable than fbsplash. Seeking the same golden rule it can take about 5 or 6 years to get that patch in vanilla (if ever goes into vanilla, which I highly doubt) |
from the lkml i got the impression the larger problem was with the plugin system as it can result in non-fs agnostic programs. |
The major issue was duplication of functionality. reiser4 duplicated some VFS code and library functions, and utilized wrappers unnecessarily. As far as I know, these issues have been addressed, but we need to wait for all the newly introduced bugs to be fixed before reiser4 gets into vanilla. |
|
| Back to top |
|
|
tranquilcool
Veteran
Joined: 25 Mar 2005
Posts: 1179
|
| Posted: Tue Oct 04, 2005 6:20 am Post subject: |
|
|
1)first patch the 2.6.13 kernel with reiser4-2.6.13-1 from namesys,
2)then go get the IKML.org patch ( copy and paste in and editor then save it),
3) cd into linux-2.6.13/fs/reiser4 then do,
4) patch -p1 < the IKLM.org you saved
the kernel then compiled for me and is workin fine. no probs so far.
_________________
this is a strange strange world. |
|
| Back to top |
|
|
iphitus
Apprentice
Joined: 03 Aug 2005
Posts: 226
|
| Posted: Tue Oct 04, 2005 7:09 am Post subject: |
|
|
| tranquilcool wrote: | 1)first patch the 2.6.13 kernel with reiser4-2.6.13-1 from namesys,
2)then go get the IKML.org patch ( copy and paste in and editor then save it),
3) cd into linux-2.6.13/fs/reiser4 then do,
4) patch -p1 < the IKLM.org you saved
the kernel then compiled for me and is workin fine. no probs so far. |
Or grab one of the patchsets that contain reiser4, such as archck, or the more developmental nitro.
btw, it's LKML - Linux Kernel Mailing List, it's a lowercase L, l, not IKML. |
|
| Back to top |
|
|
|
Unsupported Software
