Bug 129026
Summary: | rename(2) system function does not work properly | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Evgeny Baskakov <ebaskakov> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-16 04:17:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Evgeny Baskakov
2004-08-03 06:34:46 UTC
rename goes straight to the kernel, so I don't see how this could be a glibc bug. which filesystem, what kind of fs errors and BTW, could you post the strace of actual execution on your box? The fs type is ext3. Here is a sample output of the e2fsck program (command line is 'e2fsck -ycfv /dev/hda11'): Inode 218081 ref count is 2, should be 1 Inode 231585 ref count is 2, should be 1 Unattached inode 247918 Connect to /lost+found? <YES> Inode 264534 ref count is 2, should be 1 Inode 278235 ref count is 2, should be 1 The strace log is quite large (22 Mb). There is nothing unusal about rename calls: grepped list shows that all rename() calls return zero. Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |