On 2007-06-06 11:10, Xu CanHao wrote:
So maybe I'd suggest anybody take the _official_ reiser4 patch-set and
_vanilla_ kernel source, these things should provide the maximum
stability. My root filesystem with reiser4 never loses data.
I fully agree, as long as there _exists_ a current official
On 2007-06-04 13:41, Edward Shishkin wrote:
When performing mapping read (needed for execution, etc) reiser4
converts small files from tails to extents and back (your /bin/sleep
is less then 4 * blocksize, right?)
Yes, it's 15k.
The conversion is done on disk, even when mounted read only?
So maybe I'd suggest anybody take the _official_ reiser4 patch-set and
_vanilla_ kernel source, these things should provide the maximum
stability. My root filesystem with reiser4 never loses data.
Ingo Bormuth wrote:
On 2007-06-03 03:10, Edward Shishkin wrote:
Ingo Bormuth wrote:
Hm, same here. I lost /bin/sleep several times.
Would you please describe the problem in more details?
What kernel version? What does I lost /bin/sleep mean?
Does it mean that:
1.
On 2007-06-03 03:10, Edward Shishkin wrote:
Ingo Bormuth wrote:
Hm, same here. I lost /bin/sleep several times.
Would you please describe the problem in more details?
What kernel version? What does I lost /bin/sleep mean?
Does it mean that:
1. /bin/sleep was truncated to 0 bytes, i.e. ls -l
On 2007-05-30 15:03, David Masover wrote:
Only, recently, these fsck-a-thons started happening more and more often, and
I started to lose random files. They'd just be silently truncated to 0 bytes.
And not files I was writing a lot -- I'm talking about things
like /bin/mount.
Hm, same
Ingo Bormuth wrote:
On 2007-05-30 15:03, David Masover wrote:
Only, recently, these fsck-a-thons started happening more and more often, and
I started to lose random files. They'd just be silently truncated to 0 bytes.
And not files I was writing a lot -- I'm talking about things
like
On Tuesday 29 May 2007 07:36:13 Toby Thain wrote:
but you can't
mention using reiserfs in mixed company without someone accusing
you of
throwing your data away.
People who repeat this rarely have any direct experience of Reiser;
they repeat what they've heard; like all myths and
Hello
On Wednesday 30 May 2007 17:25, David Masover wrote:
On Tuesday 29 May 2007 07:36:13 Toby Thain wrote:
but you can't
mention using reiserfs in mixed company without someone accusing
you of
throwing your data away.
People who repeat this rarely have any direct experience
Hello
On Tuesday 29 May 2007 16:36, Toby Thain wrote:
I have always found reiser3 to be rock solid
My experienced too, over many server years.
but you can't
mention using reiserfs in mixed company without someone accusing
you of
throwing your data away.
People who repeat this
On 30-May-07, at 10:25 AM, David Masover wrote:
On Tuesday 29 May 2007 07:36:13 Toby Thain wrote:
but you can't
mention using reiserfs in mixed company without someone accusing
you of
throwing your data away.
People who repeat this rarely have any direct experience of Reiser;
they repeat
-list@namesys.com
Sent: Wednesday, May 30, 2007 9:42:01 AM
Subject: Re: Filesystem corruption
On 30-May-07, at 10:25 AM, David Masover wrote:
On Tuesday 29 May 2007 07:36:13 Toby Thain wrote:
but you can't
mention using reiserfs in mixed company without someone accusing
you of
throwing your
On 30-May-07, at 2:22 PM, devsk wrote:
I think people just like to spread FUD without doing any analysis
of what really caused the FS corruption.
I fear you're right. OTOH, filesystem developers on this list (and
others including ZFS list) tend to be extremely meticulous.
--Toby
On Wednesday 30 May 2007 11:42:01 Toby Thain wrote:
But does it cause data loss? One usually sees claims that reiserfs
ate my data, or I heard reiserfs ate somebody's data, but without
supplying a root cause - bad memory? powerfail? bad disk? etc.
Power failure shouldn't kill a filesystem,
On Wednesday 30 May 2007 12:22:17 devsk wrote:
I have used R4 for a year now and I have had to reset my PC,
troubleshooting problems with vmware/mythtv/cisco vpn client/nvidia, so
many times that its not even funny! And R4 didn't give me any problems even
once. It boots right up, without any
On Wednesday 30 May 2007 11:02:26 Vladimir V. Saveliev wrote:
Ordinarily I like to help debug things, but not at the risk of my data.
Maybe I'll try again later, and see if I can reproduce it in a VM or
somewhere safe...
that would be great, thanks
Keep in mind, it's unlikely, given I
PROTECTED]
Cc: Toby Thain [EMAIL PROTECTED]; ReiserFS List reiserfs-list@namesys.com
Sent: Wednesday, May 30, 2007 1:03:14 PM
Subject: Re: Filesystem corruption
On Wednesday 30 May 2007 12:22:17 devsk wrote:
I have used R4 for a year now and I have had to reset my PC,
troubleshooting problems
Hello
On Tuesday 29 May 2007 08:18, Tracy R Reed wrote:
Laurent CARON wrote:
Seems to me it is a filesystem corruption.
Did I miss it or did not a single person ask you if this happened with
reiserfs 3 or 4?
Laurent mentioned rebuild-tree mode of reiserfsck. So the problem happened
Hello
On Monday 28 May 2007 22:16, Laurent CARON wrote:
Christian Kujau a écrit :
Please try to check the fs with a current version of reiserfsprogs
first. As the manpage advises, try --check first and use
--rebuild-tree only if you know what you're doing, IOW: have a current
backup.
I have always found reiser3 to be rock solid
My experienced too, over many server years.
but you can't
mention using reiserfs in mixed company without someone accusing
you of
throwing your data away.
People who repeat this rarely have any direct experience of Reiser;
they repeat what
?- ? ? ??? new
drwx-- 2 lcaron mail48 2007-05-24 19:16 tmp/
The entry that scares me is
?- ? ? ??? new
Seems to me it is a filesystem corruption.
Any other solution than rebuild-tree ?
Did you try rm -rf new?
Thanks
Laurent
Vladimir V. Saveliev a écrit :
Did you try rm -rf new?
$ rm -rf new
rm: cannot lstat `new': Permission denied
Hello
On Monday 28 May 2007 18:10, Laurent CARON wrote:
Vladimir V. Saveliev a écrit :
Did you try rm -rf new?
$ rm -rf new
rm: cannot lstat `new': Permission denied
Is there anything from reiserfs in system logs?
Vladimir V. Saveliev a écrit :
Is there anything from reiserfs in system logs?
Nothing from reiserfs/kernel in
I did experience a similar bug on another computer a while ago (this bug
was fixed by rebuilding the tree).
[resending, because lncsa.com bounced my mail]
On Mon, 28 May 2007, Christian Kujau wrote:
On Sun, 27 May 2007, Laurent CARON wrote:
The entry that scares me is
?- ? ? ??? new
Seems to me it is a filesystem corruption.
Any other solution than rebuild
Christian Kujau a écrit :
Please try to check the fs with a current version of reiserfsprogs
first. As the manpage advises, try --check first and use
--rebuild-tree only if you know what you're doing, IOW: have a current
backup.
Over the past few years, i experienced a few reiser corruption
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 28 May 2007, Laurent CARON wrote:
Always ran check which told me to run fix-fixable or rebuild-tree, which I
did after ensuring of backup reliability, and the error was corrected (after
eventually losing a few files i fortunately had in the
that scares me is
?- ? ? ??? new
Seems to me it is a filesystem corruption.
Any other solution than rebuild-tree ?
Thanks
Laurent
Hello!
On Thu, Aug 14, 2003 at 12:05:28AM +0800, Locke wrote:
the files. I'm guessing the reason why it recovered so little was
because that because I was running a 7.8GB+40GB LVM and the 40GB
pyhsical volume wasn't working and left it with only 7.8GB.
Yes of course.
is_tree_node: node
Hello,
Though this machine will be replaced by a real server in a few month, I'm
still rather worried what happend. Even if its 'only' a hardware memory
problem this means lots of trouble for us -- on the one hand it seems not
to be memtest86 detectable and on the other hand our programs
On Friday 21 March 2003 08:32, you wrote:
Hello!
On Thu, Mar 20, 2003 at 07:23:48PM +0100, Bernd Schubert wrote:
Hm, interesting.
And what are the differences? How big are they?
Since it are binaries files, a colleague had the idea to use hexdump and
diff, so the command for the
Hi,
So, the beam of X-rays run through the memory module corrupting some bits?
;) This stuff should not have been written to disk, so probably
plain reboot should fix everything? Can you test that?
indeed after rebooting everything is fine again. We will run another memtest86
during the
Hello!
On Fri, Mar 21, 2003 at 02:01:38PM +0100, Bernd Schubert wrote:
So, the beam of X-rays run through the memory module corrupting some bits?
;) This stuff should not have been written to disk, so probably
plain reboot should fix everything? Can you test that?
indeed after rebooting
I've learn in the school that if you put some bit amount of plumbum in
between some area and source of radiation, chances are radiation that will
reach the protected area will be of much lesser strenght.
In fact you might go to those guys and ask them what matherial (and how
much of it) is
On Fri, 21 Mar 2003 14:07, Oleg Drokin wrote:
I've learn in the school that if you put some bit amount of plumbum in
It's better known in English as lead.
The problem with lead is that it's poisonous and soft. Having to wash your
hands after touching your computer could get annoying.
Other
Quoting Vitaly Fertman ([EMAIL PROTECTED]):
Hi,
Hello,
The exact commands used are:
resize_reiserfs -s 400G /dev/vg01/stuff
lvreduce -l 16693 /dev/vg01/stuff
pvmove -v /dev/md1
vgreduce -v vg01 /dev/md1
resize_reiserfs /dev/vg01/stuff
reiserfsck --check /dev/vg01/stuff
Thanks Oleg,
sorry for the late response (i was out of the office) , you may find
the
following information on the last crash useful :-
+++
3 04:32:37 devo kernel: vs-13075: reiserfs_read_inode2: dead inode read from
disk [854 1695654 0x0 SD]. This is likely to be
Hello,
First something about my setup:
md0: 8x80 GB in a RAID5 configuration
md1: 4x160 GB in a RAID5 configuration
/dev/vg01/stuff: the union of md0 and md1 done with lvm.
dark:/mnt# reiserfsck -V
-reiserfsck, 2002-
reiserfsprogs 3.x.1a
dark:/mnt# resize_reiserfs -v
Hello!
On Thu, Jun 06, 2002 at 02:00:01PM -0400, Kurt wrote:
error stating the file pointed to nowhere.
I was unable to complete a reiserfsck --fix-fixable because of the length of
time that this (fsck) process took since this was an unscheduled downtime.
During the weekend i will attempt
(Embedded
image moved Kurt [EMAIL PROTECTED]
to file: 06/06/2002 02:00 PM
pic11654.pcx)
(Embedded
image moved Kurt [EMAIL PROTECTED]
to file: 06/06/2002 02:00 PM
pic29967.pcx)
41 matches
Mail list logo
