All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artur Makówka" <juice@ursynow.2a.pl>
To: Hans Reiser <reiser@namesys.com>
Cc: John Gilmore <jgilmore@glycou.com>,
	reiserfs-list@namesys.com,
	Alexander Zarochentcev <zam@namesys.com>
Subject: Re: Slowdown is gone & apt-get works with updated reiser4. So nevermind...
Date: Sun, 13 Nov 2005 01:55:06 +0100	[thread overview]
Message-ID: <43768EEA.90307@ursynow.2a.pl> (raw)
In-Reply-To: <43765E8D.7030104@namesys.com>

Hans Reiser wrote:
> John Gilmore wrote:
> 
>> On Saturday 12 November 2005 06:38, Hans Reiser wrote:
>>  
>>
>>> Being seamless, cleanly implemented, and requiring little or no admin
>>> work, matters a lot to end users.
>>>    
>>>
>> Amen, Brother!
>>
>>
>>  
>>
>>> Yes, users can do what you said with rsync, but it is important that it
>>> be no more work than specifying a --use-versioning mount option, and
>>> even that is beyond most users (but that is where defaults come in to
>>> help them).
>>>
>>> The namespace for the past versions should be as cleanly done as WAFL
>>> does them.  Whether space gets freed automatically when space gets <10%
>>> is another mount option.  Where we might do better than WAFL is in
>>> allowing touching filename/..../checkin to cause a version to get
>>> recorded, rather than doing it at particular times.
>>>
>>> Hans
>>>    
>>>
>> Of particular concern is that the name space should (somehow) 
>>
> somehow = filename/versions/version_number and ls -l filename/versions ?
> 
>> allow me to 
>> easily grab version by date, even if the file hadn't changed for the two 
>> weeks before that, and in fact still hasn't changed... Make it really easy to 
>> grab all or some files by wildcard and with a specific revision, even when 
>> not every file changed with that revision.
>>
>> Oh, BTW. "The slowdown" as I called it is still there. I guess I spoke to 
>> soon. The specific symptom is that the effected process locks for a time, 
>> usually just a second or two, but sometimes a minute or two and and at least 
>> once for many many minutes. I think that the crash (soft lockup) that I 
>> reported earlier is related as well. And it sounds like the comment that 
>> rvalles had about lockups with mmaped files, except that it doesn't lock up 
>> permanently. Just for a second or three usually.
>>
>>  
>>
> zam, please comment.
> 

one more thing im pretty sure of - the 2.6.13mm3 without any reiser4 
additional patches (just clean 2.6.13mm3 as it has reiser4 already 
built) is working fine.

i mean, im not sure if this bug still exists here, but im 100% sure i 
can write vim files easy without any downtime, so this is big difference.

so for everyone with this bug - try clean 2.6.13mm3 from kernel.org. It 
worked for me. i will wait with this kernel for a patch to stable line.

Also - i will test it a little more tomorrow to be sure that this 
version is bug free.


  reply	other threads:[~2005-11-13  0:55 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 13:59 Slowdown is gone & apt-get works with updated reiser4. So nevermind John Gilmore
2005-11-11 21:22 ` Hans Reiser
2005-11-11 22:06 ` Jonathan Briggs
2005-11-12  3:07   ` michael chang
2005-11-12  6:38     ` Hans Reiser
2005-11-12  9:06       ` John Gilmore
2005-11-12 20:57         ` Artur Makówka
2005-11-12 21:28         ` Hans Reiser
2005-11-13  0:55           ` Artur Makówka [this message]
2005-11-13 12:18             ` Laurent Riffard
2005-11-13 12:25               ` Laurent Riffard
2005-11-13 12:29               ` Artur Makówka
2005-11-13 13:12                 ` Thomas Kuther
2005-11-13 14:05                   ` Artur Makówka
2005-11-14 17:48                     ` Pat Double
2005-11-14 20:22                       ` Artur Makówka
2005-11-13 14:05                   ` Ingo Bormuth
2005-11-14 19:41         ` More Slowdown Craig Shelley
2005-11-14 19:53           ` jp
2005-11-14 20:47           ` Christian Iversen
2005-11-15 14:27             ` Craig Shelley
2005-11-15 18:04               ` Laurent Riffard
2005-11-15 18:42                 ` Craig Shelley
     [not found]                   ` <437AF653.9040001@namesys.com>
2005-11-16  9:33                     ` Craig Shelley
2005-11-17  3:08               ` michael chang
2005-11-17  4:49                 ` Hans Reiser
2005-11-17 12:02                   ` Artur Makówka
2005-11-17 12:40                     ` Vladimir V. Saveliev
2005-11-17 10:34                       ` John Gilmore
2005-11-17 21:12                         ` Hans Reiser
2005-11-18 20:45                     ` Hans Reiser
2005-11-17  8:56                 ` Ingo Bormuth
2005-11-17  9:36                 ` PFC
2005-11-17 21:08                   ` Hans Reiser
2005-11-19  4:44                     ` michael chang
2005-11-12  0:56 ` Versioning Plugin Peter van Hardenberg
2005-11-12  2:24   ` Hans Reiser
2005-11-12 14:06   ` Ming Zhang
2005-11-12 21:46     ` David Masover
2005-11-12 22:05       ` Ming Zhang
2005-11-13  2:56         ` David Masover
2005-11-13  3:05           ` Ming Zhang
2005-11-13  4:23             ` Hans Reiser
2005-11-13  3:28           ` Hans Reiser
2005-11-12 22:54       ` Hans Reiser
2005-11-13  0:57         ` Ming Zhang
2005-11-13  1:55           ` michael chang
2005-11-13  1:56             ` michael chang
2005-11-13  2:13               ` Ming Zhang
2005-11-13  3:03               ` Hans Reiser
2005-11-13  2:13             ` Ming Zhang
2005-11-13  2:27             ` Hans Reiser
2005-11-13  2:32               ` Ming Zhang
2005-11-13  2:53                 ` michael chang
2005-11-13  2:56                   ` Ming Zhang
2005-11-12 22:57   ` Lares Moreau
2005-11-12 23:35     ` Hans Reiser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43768EEA.90307@ursynow.2a.pl \
    --to=juice@ursynow.2a.pl \
    --cc=jgilmore@glycou.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.