A snipet from htop:
PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
66 root 25 0 0 0 0 R 50.0 0.0 1h21:53 pdflush
3235 root 25 0 0 0 0 R 49.5 0.0 33:50.45 ent:hda6!
uname -a :
Linux mu 2.6.14-rc1-mm1 #1 PREEMPT Tue Sep 20 16:02:39 CD
David Howells wrote:
Edward Shishkin <[EMAIL PROTECTED]> wrote:
David, would you please review the following:
KEY MANAGEMENT IN REISER4
There's a mailing list for such discussions:
[EMAIL PROTECTED]
I should update the MAINTAINERS file to reflect this.
On 9/23/05, David Greaves <[EMAIL PROTECTED]> wrote:
> who's not keeping up with the linux-raid list then ;)
>
> David
> PS I'm sure assistance would be appreciated in testing and reviewing
> this few day old feature - or indeed the newer 'add a new disk to the
> array' feature.
After posting that
Fred Schaettgen wrote:
On Thursday, 22. September 2005 22:03, Edward Shishkin wrote:
Fred Schaettgen wrote:
I don't quite understand how the file plugin concept scales once we get
more of them. For instance if I want to have an additional attribute
attached to my files, which contains
Raymond A. Meijer wrote:
>On Friday 23 September 2005 11:35, Vladimir V. Saveliev wrote:
>
>Hi Vladimir,
>
>
>
>>Ray, you might want to try to mount reiser4 with -o
>>onerror=remount-ro This may help to avoid some of oopses
>>
>>
>
>I'll try this.
>
>
>
>>You need new hard drive.
>>
>>
michael chang wrote:
Second, will plugins be layerable, e.g. can I use a compression plugin
and a _seperate_ encryption plugin on the _same_ file,
There is a number of specific attributes including compression and
encryption
transform plugin ids, so user can assign it separately when creati
On Friday 23 September 2005 11:35, Vladimir V. Saveliev wrote:
Hi Vladimir,
> Ray, you might want to try to mount reiser4 with -o
> onerror=remount-ro This may help to avoid some of oopses
I'll try this.
> You need new hard drive.
I already have one (an old 80GB) but the broken one is 200GB an
Hello
Raymond A. Meijer wrote:
> On Thursday 22 September 2005 13:19, Pysiak Satriani wrote:
>
>>I might be wrong here, but bad blocks are a condition that the kernel
>>should handle without barfing oops traces,
Ray, you might want to try to mount reiser4 with -o onerror=remount-ro
This may help
