Hi,
I already answered Vladimir's posting twice - one thanks, I'll try
that and one success report. It just so happens that a LOT of mails I
send to the list never gets through, no idea why.
Could someone resend that info to the list? I'm sure others would be
interested too.
Michael
Hi,
I'm 100% happy. Now it did not stop.
Either it would haven been nessesary to run it twice or the new
version I've got from did the trick.
Good to hear that!
I thank you so much!
Now I go any buy a new disk!!!
Usually when a disk goes bad you should get a new disk FIRST, then make
an
?
--
/\
| Michael Weissenbacher [EMAIL PROTECTED] |
| http://www.dermichi.com/ |
| Email users are divided into two classes;|
| 1) Those who have effective spam-blocking
Hello,
I noticed the REISER4 RELEASED! statement in
http://www.namesys.com/download.html and wonder when it did get released
and what its status now.
it is released but from my experience the latest changes that were
necessary to prepare for inclusion into the vanilla kernel have
,
--
/\
| Michael Weissenbacher [EMAIL PROTECTED] |
| http://www.dermichi.com/ |
| The trouble with computers is that they do what you tell |
| them, not what you want. -- D. Cohen|
\/
there that the version is unstable. i'm sure
most people go straight for the vanilla kernel patch and don't bother
with mm-kernels. this puts reiser4 in a bad light imo.
kind regards,
Michael
--
/\
| Michael Weissenbacher [EMAIL
regards,
Michael
--
/\
| Michael Weissenbacher [EMAIL PROTECTED] |
| http://www.dermichi.com/ |
| In 2010, M$ Windows will be a quantum processing emulation |
| layer for a 128-bit mod of a 64-bit
to the
reiser4 partition after the error. It never corrupted any data though,
fsck.reiser4 always reported a consistent fs. I'll try to trigger that
problem again and make another post.
--
/\
| Michael Weissenbacher [EMAIL PROTECTED
/tail_conversion.c:29
kind regards,
--
/\
| Michael Weissenbacher [EMAIL PROTECTED] |
| http://www.dermichi.com/ |
\/
in /lost+found. Should I run fsck with --build-fs then? Also, can this be
short answer: yes, this renamed the files in lost+found (in my case)
so that i could delete them.
regards,
michael
rm /lost+found/lost_name_*
gives:
rm: cannot remove `/lost+found/lost_name_5447b:6b68746d6c6361:27e2e2r?\t
v\310:H\327\377\257O\275\275: v\310:[EMAIL PROTECTED]:\200r?\t': No such
file
or directory
had the same problem, it is related to fsck which computes hashes the
wrong way if filenames are
Michael Weissenbacher wrote:
rm /lost+found/lost_name_*
gives:
rm: cannot remove `/lost+found/lost_name_5447b:6b68746d6c6361:27e2e2r?\t
v\310:H\327\377\257O\275\275: v\310:[EMAIL PROTECTED]:\200r?\t': No such
file or directory
had the same problem, it is related to fsck which computes hashes
Hi, we had a bug report that Apache httpd logs a spurious error for
every file served from a reiser4 filesystem, because httpd assumes that
/path/to/file/.htaccess (where /path/to/file is a normal file) returns
ENOENT or ENOTDIR, but reiser4 returns EACCES in this case.
Can someone explain the
I'm using kernel 2.6.9-rc1-mm1 (patched for the page-size bug) and
reiser4progs1.0.0. I am able to reproduce a wrong bytes problem by
doing the following:
# dd if=/dev/urandom bs=4096 count=1048576 of=/mnt/tmp/testfile
# umount /mnt/tmp
# fsck.reiser4 /dev/sda1
...
FSCK: Node (45223670), item
Even though both file sets contain umlauts, or perhaps more accurately extended ASCII chartacters, there is something distinctive in the failure set: the umlauts/extended characters appear after the 15th character. If you are using REISER4_LARGE_KEYS, the first fifteen characters will be shifted
- 2.6.9-rc1-mm1 has a bug that affects all filesystems (pointed out
earlier today). so don't use if you love your data ;)
Can you tell us more about this bug?
(I'm using 2.6.9-rc1-mm1 and would like to know, what will happen ;) )
See:
the cause of the problem.
anyone got an idea?
thanks,
michael weissenbacher
17 matches
Mail list logo
