[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bugs #9960] High 16 bits of st_nlink are sometimes corrupted

From: Ognyan Kulev
Subject: [bugs #9960] High 16 bits of st_nlink are sometimes corrupted
Date: Wed, 11 Aug 2004 00:42:13 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5

This mail is an automated notification from the bugs tracker
 of the project: The GNU Hurd.

[bugs #9960] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9960>
Project: The GNU Hurd
Submitted by: Ognyan Kulev
On: Tue 08/10/2004 at 18:14

Category:  None
Severity:  5 - Average
Priority:  5 - Normal
Item Group:  None
Resolution:  None
Assigned to:  None
Originator Name:  
Originator Email:  
Status:  Open
Reproducibility:  Intermittent
Size (loc):  None
Effort:  0.00

Summary:  High 16 bits of st_nlink are sometimes corrupted

Original Submission:  This is in hurd 20040508-2.  I wonder why nobody noticed 
it before.

Sometimes st_nlink is reported as big number, like 135790593. Lower 16 bits are 
always correct, and high 16 bits, if they are corrupted, are in range 
0x815-0x818.  rpctrace shows that ext2fs/libdiskfs is to be blamed, not glibc 
or programs.

ls -l many times shows unstable behaviour.   Sometimes all is correct.  
Sometimes for a given time specific files have corrupted st_nlink, and this 
changes after some time.  Sometimes each ls -l gives different corrupted 

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]