Hello.
Do you have more than one mounted reiser4 partition?
Thanks,
Lena
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
Hello
On Mon, 2005-06-06 at 10:00, R Deepak wrote:
Greets!
Can I ask support questions here? If not, sorry.. :(
I have a RAID0 config with 2 80GB SATA disks. I screwed up during an install
and the super block got overwritten.
When I ran reiserfsck on /dev/md0, it asked me to use
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
Hello.
Would you please send me the output of
# lvdisplay --maps
# pvdisplay --maps
Thanks,
Lena
Matthias Barremaecker wrote:
Hi,
If I check my lvm partition, then I have bad blocks.
To know what hd there's bad, I have to check the hd's seperatly.
but what do i check and do I use the
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
On Monday 06 June 2005 14:04, you wrote:
Hello
On Mon, 2005-06-06 at 10:00, R Deepak wrote:
Greets!
Can I ask support questions here? If not, sorry.. :(
I have a RAID0 config with 2 80GB SATA disks. I screwed up during an
install and the super block got
Nikita Danilov wrote on Fri, 3 Jun 2005 15:15:08 +0400:
This is exactly what some application do. Here is how transactions can
be implemented in the POSIX file system:
- you have a symlink ./d.active pointing to the current directory
under which some sub-tree of interest is located;
-
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
Nikita Danilov wrote:
Hans Reiser writes:
Nikita Danilov wrote:
But cycles are solvable in current file systems too: they simply do
not exist there.
Yes, but Nikita, cycles represent semantic functionality that has value
because being able to embody more expressions means
Hello.
Would you please send us the following :
1. # cat /proc/mdstat
2. the raid configuration file wich you used for creating this md0?
Thanks,
Lena
Deepak Ram wrote:
On Monday 06 June 2005 14:04, you wrote:
Hello
On Mon, 2005-06-06 at 10:00, R Deepak wrote:
Greets!
12 matches
Mail list logo
