> " " == Alexander Viro <[EMAIL PROTECTED]> writes:
> On 30 May 2001, Trond Myklebust wrote:
>> Al: Is there any reason why the cases
>>
>> if (!inode->i_nlink)
>>
>> and the 'magic nfs path' should be treated differently?
>> Personally, I'd rather prefer to mer
On 30 May 2001, Trond Myklebust wrote:
> The reason we haven't seen this before is that we had 'force_delete'
> that would always set i_nlink = 0. Unfortunately force_delete is toxic
> to mmap(), as it will discard any dirty pages rather than flushing
> them to storage, so it was removed in the
> " " == Alexander Viro <[EMAIL PROTECTED]> writes:
> On Tue, 29 May 2001, Gergely Tamas wrote:
>> Warning (compare_maps): mismatch on symbol partition_name ,
>> ksyms_base says c01c4020, System.map says c0154160. Ignoring
>> ksyms_base entry kernel BUG at inode.c:486!
On Tue, 29 May 2001, Gergely Tamas wrote:
> Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says
>c01c4020, System.map says c0154160. Ignoring ksyms_base entry
> kernel BUG at inode.c:486!
[snip]
_Lovely_. NFS, apparently on revalidate path, doesn't care to hold on
Hi!
Kernel 2.4.5 & ReiserFS umount-fix patch
2 CPU SMP, 1 Gb memory
During working on an NFS mounted drive ``/mnt/somewhere'' I got this
oops (multiple times, so it is reproducable).
Thanks in advance,
Gergely
---
somewhere % pwd
/mnt/somewhere
somewhere % ls -l
<...OOPS...>
---
ksymoops 2.4
5 matches
Mail list logo