lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Mon, 05 May 2008 20:29:04 +0200
From:	Jesper Krogh <jesper@...gh.cc>
To:	Ray Lee <ray-lk@...rabbit.org>
CC:	"Randy.Dunlap" <rdunlap@...otime.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Many open/close on same files yeilds "No such file or directory".

Ray Lee wrote:
> On Mon, May 5, 2008 at 10:54 AM, Jesper Krogh <jesper@...gh.cc> wrote:
>> Randy.Dunlap wrote:
>>
>>> On Mon, 5 May 2008, Jesper Krogh wrote:
>>>
>>>
>>>> Jesper Krogh wrote:
>>>>
>>>>> Ray Lee wrote:
>>>>>
>>>>>> BTW, I may have missed this earlier, but does it happen *anywhere*
>> on
>>>>>> the troublesome filesystem (ie, in a newly created subdirectory)?
>>>>>>
>>>>> Yes. It is reproducible on a newly created subdirectory on the
>>>>> filesystem.
>>>>>
>>>> Now I've created a new filesystem. (resized the original LVM-volume to
>> half
>>>> and created a new ext3 one next to it). The problem persists on this new
>>>> filesystem.
>>>>
>>>> Just guessing, can there be something timing related in clearing the
>> FS-cache
>>>> for the filesystem?
>>>>
>>>> Any other suggestions/pointers.
>>>>
>>> Hi,
>>>
>>> Has anyone else been able to reproduce this problem?
>>>
>>  No, and out of my systems. I only have this external SCSI-IDE-raid device I
>> can reproduce it on. The internal system disks doesnt allow me to reproduce
>> it on the same installation.
> 
> I'd been meaning to ask what the topology was. External, eh? Are you
> sure the enclosure, cabling, and card/connectors are all good? Have
> you tried swapping out cables?

It is new SCSI-controller, new cable and new terminator put onto it. But
(just enlighten me), if I had problems at this level I'd expect the
serverlog to be full of SCSI/FS-related errors and not just a single
syscall, that doesn't even touch the array due to caching, to be
failing.

Jesper
-- 
Jesper
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ