Bug 1578405 - EIO errors when updating and deleting entries concurrently
Summary: EIO errors when updating and deleting entries concurrently
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Xavi Hernandez
QA Contact:
URL:
Whiteboard:
: 1397283 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-15 14:00 UTC by Xavi Hernandez
Modified: 2020-03-12 13:02 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-12 13:02:10 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 20025 0 None Open locks: prevent deletion of locked entries 2020-02-26 07:40:20 UTC

Description Xavi Hernandez 2018-05-15 14:00:35 UTC
Description of problem:

When files/directories are continuously updated and deleted concurrently. At some point some of them get corrupted and accessing them gives EIO errors.

Version-Release number of selected component (if applicable): mainline


How reproducible:

Most of the times

Steps to Reproduce:
1. Create a distributed-disperse volume
2. Mount it on two clients
3. On one client run "while true; do mkdir a;done"
4. On the other client run "while true;do mv a b; mv b a;done"
5. Wait some minutes
6. Stop the jobs started on steps 3 and 4
7. Run "rm -rf *" from one client

Actual results:

The rm failed with EIO error

Expected results:

The rm shouldn't fail

Additional info:

Comment 1 Worker Ant 2018-05-15 14:04:54 UTC
REVIEW: https://review.gluster.org/20025 (locks: prevent deletion of locked entries) posted (#1) for review on master by Xavi Hernandez

Comment 2 Xavi Hernandez 2018-10-25 14:20:18 UTC
*** Bug 1397283 has been marked as a duplicate of this bug. ***

Comment 3 Worker Ant 2020-03-12 13:02:10 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/990, and will be tracked there from now on. Visit GitHub issues URL for further details


Note You need to log in before you can comment on or make changes to this bug.