rvalles wrote:
On Tue, Jul 11, 2006 at 03:04:20PM -0700, Hans Reiser wrote:
Please feel free to comment on this list and the order of its tasks:
4) review complaints of pauses while using reiser4 --- size of task
unknown, and it is also unknown how much we may have fixed it while
writing
Christoph Lameter wrote:
On Thu, 13 Jul 2006, Hans Reiser wrote:
Christoph Lameter wrote:
Will there be any NUMA /SMP fixes? Reiserfs performance is severely
impacted at higher processor counts by the mandatory centralized locking
in both read and write paths in the filesystem.
Hello,
I am almost sure that unclean shutdowns happen in those systems. We have tried
to reproduce removing power each 5 minutes and the filesystem wasn't
suffering corruption. Perhaps it's related, but I don't know.
I have talked about 'Datalogging patches' because it's the only thing
Hello
On Fri, 2006-07-14 at 10:25 +0200, Francisco Javier Cabello wrote:
Hello,
I am almost sure that unclean shutdowns happen in those systems. We have
tried
to reproduce removing power each 5 minutes and the filesystem wasn't
suffering corruption. Perhaps it's related, but I don't know.
Yes. I have a sef of system with the same main board, memory,
microprocessor... They are identical. The difference is the conditions where
they are working. Perhaps the cpu load average is difference, the amount of
data they are writting, the number of power failure...
I am going to send you
Hello Vladimir,
# reiserfsck -l /tmp/reiserfsck.log -y --check /dev/hdc1
Standard output:
==
Will read-only check consistency of the filesystem on /dev/hdc1
Will put log info to '/tmp/reiserfsck.log'
###
reiserfsck --check started at
Hello
On Fri, 2006-07-14 at 14:20 +0200, Francisco Javier Cabello wrote:
Hello Vladimir,
# reiserfsck -l /tmp/reiserfsck.log -y --check /dev/hdc1
Standard output:
==
Will read-only check consistency of the filesystem on /dev/hdc1
Will
Eric Dumazet [EMAIL PROTECTED] wrote:
On Wednesday 12 July 2006 18:42, Jeff Mahoney wrote:
On systems with block devices containing slashes (virtual dasd, cciss,
etc), reiserfs will fail to initialize /proc/fs/reiserfs/dev due to
it being interpreted as a subdirectory. The generic block
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bodo Eggert wrote:
Eric Dumazet [EMAIL PROTECTED] wrote:
On Wednesday 12 July 2006 18:42, Jeff Mahoney wrote:
On systems with block devices containing slashes (virtual dasd, cciss,
etc), reiserfs will fail to initialize /proc/fs/reiserfs/dev
On Fri, 14 Jul 2006 00:01:49 -0700
Hans Reiser [EMAIL PROTECTED] wrote:
rvalles wrote:
I believe those two are related. I'm having the pauses (of many
minutes at times!) when writing to reiser4. It seems it is triggered
mostly by the use of fsync(); NFS in sync mode manages to trigger it
way
I am seeing a lot of these errors:
ReiserFS: sda7: warning: vs-8115: get_num_ver: not directory or indirect
item
I did a google search and all I see is emails back from 2004/2005 about
it being a issue with the 2.6.8 kernel. Are these warnings something I
should run reiserfsck on the partition
On 7/14/06, Michael T. Dean [EMAIL PROTECTED] wrote:
On 07/14/2006 09:31 PM, Carl Fongheiser wrote: On 7/14/06, *Ryan Steffes* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote: I've never seen ls do this before, at least, not for root.Any idea what could cause it? # ls ls:
12 matches
Mail list logo
