Hello!
On Wed, Aug 21, 2002 at 07:06:56AM +, Sean Rima wrote:
> I am getting a couple of Input/Output errors on files and cannot remove the files.
>In fact if I touch them, my pc freezes.
>
> It is a Linux 2.2.20 with reiserfs compiled, the HD is reiser. Is there anyway to
>use reiserfsck
Originally to: All
I am getting a couple of Input/Output errors on files and cannot remove the files. In
fact if I touch them, my pc freezes.
It is a Linux 2.2.20 with reiserfs compiled, the HD is reiser. Is there anyway to use
reiserfsck to sort these errors. The files lay on the root
/ hd
S
Hello!
On Tue, Aug 20, 2002 at 05:17:01PM +0200, Javier Marcet wrote:
> When applying the second of the patches available under
> reiserfs-for-2.4/2.4.19.pending/testing I get corruptions on any write
> comitted to ANY filesystem, including ram.
This is very strange, I cannot reproduce anything
Hello!
On Tue, Aug 20, 2002 at 04:24:13PM -0400, Chris Mason wrote:
> make sure it was valid, regardless of where you stored it. The problem
> is that if you store it in the tree somehow, you've got a chicken and
> egg problem that you can't read the list until the tree is good and you
> can re
Hello!
On Tue, Aug 20, 2002 at 11:26:32PM -0400, [EMAIL PROTECTED] wrote:
> > Great, I just found that we forgot to enable preallocation with new block
> > allocator by default. This is easily fixable of course.
> Is that in the 2.5.patch:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=10298419
>>> Is regression going away if you pass this mount option to reiserfs:
>>> -o alloc=preallocmin=4:preallocsize=9
>> Yes.
> Great, I just found that we forgot to enable preallocation with new block
> allocator by default. This is easily fixable of course.
Is that in the 2.5.patch:
http:/
On Mon, 2002-08-19 at 06:20, Oleg Drokin wrote:
> Hello!
>
> On Mon, Aug 19, 2002 at 02:07:26PM +0400, Hans Reiser wrote:
>
> > >He suggests that user should specify list of bad blocks each time user runs
> > >reiserfsck.
> > This sounds reasonable. You can probably even have a default location
When applying the second of the patches available under
reiserfs-for-2.4/2.4.19.pending/testing I get corruptions on any write
comitted to ANY filesystem, including ram.
I cannot give more specifics than adding that patch, doing a simple test
like creating a tar.bz2 out of a folder on my HD (be i
On Tue, 2002-08-20 at 10:24, Serge Kolodeznyh wrote:
>
> Last patch doesn't apllied :-(
>
> [root@helios linux-2.4.19]# gzip -cd kinoded-8-2.4.19-pre3.diff.gz |
> patch -p1
> patching file fs/inode.c
> Hunk #4 FAILED at 698.
> Hunk #5 succeeded at 1119 (offset -1 lines).
> Hunk #7 succeeded at 1
Last patch doesn't apllied :-(
[root@helios linux-2.4.19]# gzip -cd kinoded-8-2.4.19-pre3.diff.gz |
patch -p1
patching file fs/inode.c
Hunk #4 FAILED at 698.
Hunk #5 succeeded at 1119 (offset -1 lines).
Hunk #7 succeeded at 1278 (offset -1 lines).
1 out of 7 hunks FAILED -- saving rejects to fil
Hello!
On Tue, Aug 20, 2002 at 05:12:09PM +0400, Serge Kolodeznyh wrote:
> Who know, will quota support and fs at all be working, if my kernel is
> 2.4.19 version, and make the patches for quota support from reiserfs site ?
> The problem is that reiser's patches are for 2.4.19-pre3, not clean 2.
Hi, All !
Who know, will quota support and fs at all be working, if my kernel is
2.4.19 version, and make the patches for quota support from reiserfs site ?
The problem is that reiser's patches are for 2.4.19-pre3, not clean 2.4.19.
---
Serge Kolodeznyh
Paradigma AG
Network /system administrator
On Tue, 20 Aug 2002, Hans Reiser wrote:
> Vitaly, take a look at that. Part of a good user interface is letting
> users know what tools are available. Remember, most users will
> encounter a failing drive and/or fsck on a journaling fs as a rare and
> stressful event in their lives, so it is
Matthias Andree wrote:
>Hans Reiser <[EMAIL PROTECTED]> writes:
>
>
>
>>Just taking a guess, many hard drives have difficult and time-consuming
>>procedures that they can go through to read a troublesome block. These
>>can take 20-30 seconds. Probably if they have to go through these
>>proced
Hans Reiser <[EMAIL PROTECTED]> writes:
> Just taking a guess, many hard drives have difficult and time-consuming
> procedures that they can go through to read a troublesome block. These
> can take 20-30 seconds. Probably if they have to go through these
> procedures, once they finally succeed
15 matches
Mail list logo
