Lares Moreau schrieb:
RElated...
Is there any particular reason there is not an anonCVS/SVN repository?
to make Code access easier, and not limited to the (pseudo)Official
packages?
if the website is correct, then Reiser3+4 is developed via BK:
http://www.namesys.com/code.html
Christian.
--
Thomas Raschbacher schrieb:
how would I best copy the filesystem? DD ?
dd, if that does not work then try dd_rescue:
http://www.garloff.de/kurt/linux/ddrescue/
Christian.
--
BOFH excuse #34:
(l)user error
Detlef Grittner schrieb:
An appropriate fstab entry, so a user is allowed to mount the device
looks like this:
/home/userX/data /home/userX/crypto reiserfs
user,noauto,loop=/dev/loop0,encryption=twofish256,phash=sha512,itercountk=100
so, you're using a file-backed cryptoloop
Thomas Raschbacher schrieb:
as you see it produced no errors at all so the HDD can be read fine. any
idea what could cause the problem?
looking once more on your logfiles:
Pass 1 (will try to insert 16439 leaves):
Looking for allocable blocks .. finished
0%20%40%60%80%.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
[cc'ing 4 mailing lists, please reply to *one* list only!]
hi,
every now and then i'm running some benchmarks on filesystems i really
use...here are the results:
http://nerdbynature.de/bench/prinz64/2.6.14-rc2-mm2/bonnie.html
Gabor HALASZ schrieb:
Sep 5 12:30:24 sk8n kernel: ReiserFS: dm-10: checking transaction log
(dm-10)
Sep 5 12:30:24 sk8n kernel: ReiserFS: dm-10: Using rupasov hash to sort
names
why did you choose the rupasov hash?
http://www.namesys.com/mount-options.html knows:
rupasov: [...] Never use
Gregory Maxwell schrieb:
Someone might want to update the information on reiser4 at:
http://en.wikipedia.org/wiki/Comparison_of_file_systems
yeah, i noticed this too some time ago. so, what's the
- Maximum filename length
- Allowable characters in directory entries (e.g. Any byte except
evilninja schrieb:
- Maximum filename length
- Maximum pathname length (currently No limit defined -- is this true?)
in the thread REISERFS_MAX_NAME and ENAMETOOLONG it is stated, that max.
filename length is not a kernel limit but a libc limit of 255 chars.
right? an in the same thread
Dr. Giovanni A. Orlando schrieb:
This table is interesting but have really no sense the no inclusion of
a minimal comparision about performance.
double negation...if i understand you correctly, you want a benchmark
comparison of the compared filesystems? uh, you know how hard it is to
compare
Bedros Hanounik schrieb:
mkfs.reiserfs -l label will overwrite the old data; is there a way to edit
the old lable w/o reformating the disk, other than hexedit the disk?
reiserfstune -l LABEL
should do the job.
(and xfs_admin for XFS, jfs_tune for JFS ;)
--
BOFH excuse #219:
Recursivity.
Ronald Moesbergen schrieb:
Well, I just successfully reproduced this without the nvidia module
loaded. The oops looks very similar:
[...]
kernel: Modules linked in: vmnet vmmon
kernel: CPU:1
kernel: EIP:0060:[lock_object+84/127]Tainted: P VLI
well, the kernel is still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M schrieb:
It dies within about 30 seconds of issuing the tar command and is
repeatable. So the question is why is the filesytem corrupt?
hm, bad memory? bad cabling? running memtest86 overnight just to be sure
could help. and: can you reproduce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Gear schrieb:
The problem has occurred looks like a hardware problem (perhaps
memory). Send us the bug report only if the second run dies at
the same place with the same block number.
sodoes it? is it reproduceable on a 2nd run? also with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Any suggestions for performance/latency benchmark suites, preferrably
automated, are welcome, of course ;)
fwiw, i did some benchmarks, and will do with new hardware soon:
Christian Mayrhuber wrote:
I think the sentence Additional patches are needed
for NFS and quotas, please see http://www.namesys.com/ for links.
should be dropped in 2.6.
maybe the patch could go in?
--
BOFH excuse #182:
endothermal recalibration
--- linux-2.6/fs/Kconfig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Worley wrote:
I find the root partition an invaluable part of the system. So, I'm not
going to destroy it on purpose. I'm not quite sure how to boot without
a root partition ;)
you did backup at least /etc , didn't you? if so, then a quick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Worley wrote:
On Mon, 2004-09-27 at 08:44, Vitaly Fertman wrote:
# ./fsck/reiserfsck /dev/system/lvol0
reiserfsck 3.6.18 (2003 www.namesys.com)
Failed to open the device '/dev/system/lvol0': No such device or address
it seems
open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nikita Danilov wrote:
evilninja writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, Christian evilninja :)
um, yes, it just sticks ;-)
But in reiser4 file.txt _is_ a directory. That's the whole point: it
contains other objects
18 matches
Mail list logo
