linux-ext4 - [Bug 75621] New: Permission denied trying to touch a file; happens randomly; both ext3 and GPFS

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-75621-13602@https.bugzilla.kernel.org/>
Date:	Tue, 06 May 2014 18:45:11 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 75621] New: Permission denied trying to touch a file; happens
 randomly; both ext3 and GPFS

https://bugzilla.kernel.org/show_bug.cgi?id=75621

            Bug ID: 75621
           Summary: Permission denied trying to touch a file; happens
                    randomly; both ext3 and GPFS
           Product: File System
           Version: 2.5
    Kernel Version: 3.0.13-0.27
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
          Assignee: fs_ext3@...nel-bugs.osdl.org
          Reporter: phillip.l.viana@...il.com
        Regression: No

Hi,

I am running a benchmark against DB2 in my cluster with several ext3 (SSD) and
GPFS file systems. After running the benchmark for around two days I noticed
that one of the nodes rebooted and that was due to an error touching a file.
The file was being touched by one of the HA monitors of Tivoli System
Automation.

I immediately tried to reproduce the error by touching the file again manually.
I touched the file a few times successfully, then out of the blue I got a
"Permission denied" error. Right after that I kept touching the file and got no
error message.

CPU utilization and I/O utilization were NOT at their peaks. 

This error keeps happening randomly and therefore it is difficult to reproduce.
It has happened both on a GPFS file system and an ext3 file system. Also I
don't have much information on the internals of this problem.

Do you have suggestions on how to instrument/debug/monitor the error so that I
can move on with the investigation and bring more info to this bug report?

Thanks

Phil

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html