On Monday 06 June 2005 22:39, Adrian Ulrich wrote:
I upgraded to Linux 2.6.11.11 using the -5 reiser4 patch.
It fixed it.. somewhat.. it's still funky:
* mkisofs doesn't crash with the new kernel, yeah!
* after running mkisofs, grub can't read the filesystem anymore..
The
Hi Vitaly,
there was a format change to work with encryption plugin in
-5 reiser4 patch. progs do not have its support yet. grub works
through the progs code so its the same problem, mkisofs is not
relevant here.
I don't think thats the problem:
It looks like a remount bug:
See [EMAIL
On Tuesday 07 June 2005 15:01, Adrian Ulrich wrote:
Hi Vitaly,
there was a format change to work with encryption plugin in
-5 reiser4 patch. progs do not have its support yet. grub works
through the progs code so its the same problem, mkisofs is not
relevant here.
I don't think
I am about the particular fsck message that appeares when you
use -5 reiser4 patch:
Ok, but i think it's still strange:
This message only re-appears if i do a:
mount -o ro /dev/md1 /somewhere
mount -o remount,rw /dev/md1 /somewhere --- !!!
umount /dev/md1
fsck.reiser4 /dev/md1 --
On Tuesday 7 June 2005 15:10, Adrian Ulrich wrote:
Ok, but i think it's still strange:
This message only re-appears if i do a:
mount -o ro /dev/md1 /somewhere
mount -o remount,rw /dev/md1 /somewhere --- !!!
umount /dev/md1
fsck.reiser4 /dev/md1 -- fsck will complain..
What happens
:00:50 fuzzy kernel: reiser4 panicked cowardly: assertion failed:
hint-blk reiser4_block_count(super)
Jun 5 16:00:50 fuzzy kernel: pins held: jnode: 0, tree: 0 (r:0,w:0), dk: 0
(r:0,w:0)
Jun 5 16:00:50 fuzzy kernel: jload: 0, txnh: 0, atom: 0, stack: 0, txnmgr: 0,
ktxnmgrd: 0, fq: 0
On Sunday 05 June 2005 18:50, Adrian Ulrich wrote:
Hi,
Well, i managed to crash reiser4 ;-)
I created an iso-image on my reiser4 filesystem (it's my rootfs)
using mkisofs. mkisofs aborted because the filesystem was full.
After freeing up some space, i ran mkisofs again and: *bam*
Adrian Ulrich wrote:
Hi,
Well, i managed to crash reiser4 ;-)
I created an iso-image on my reiser4 filesystem (it's my rootfs)
using mkisofs. mkisofs aborted because the filesystem was full.
After freeing up some space, i ran mkisofs again and: *bam*
fsck.reiser4 told me to run
what reiser4 patch do you use for this kernel?
That should be
ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.11/reiser4-for-2.6.11-4.patch.gz
I'll give -5 a try this evening
I upgraded to Linux 2.6.11.11 using the -5 reiser4 patch.
It fixed it.. somewhat.. it's still funky:
* mkisofs doesn't crash with the new kernel, yeah!
* after running mkisofs, grub can't read the filesystem anymore..
The filesystem got corrupted. (It was ok before i booted
into
Now the same thing happens again :-/
Ok, i know why it only got corrupted after using
the partition as rootfs :
My Reiser4 partition doesn't like to get remounted rw:
Running
1) mount /dev/md1 /somewhere
2) umount /dev/md1
3) mount -o ro /dev/md1 /somewhere
4) umount /dev/md1
works
11 matches
Mail list logo
