[Bugs] [Bug 1611692] New: Mount process crashes on a sharded volume during rename when dst doesn' t exist
bugzilla at redhat.com
bugzilla at redhat.com
Thu Aug 2 16:05:43 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1611692
Bug ID: 1611692
Summary: Mount process crashes on a sharded volume during
rename when dst doesn't exist
Product: GlusterFS
Version: mainline
Component: sharding
Severity: high
Priority: high
Assignee: bugs at gluster.org
Reporter: kdhananj at redhat.com
QA Contact: bugs at gluster.org
CC: bugs at gluster.org
Description of problem:
Was executing rsync to copy data within a sharded volume. And rsync internally
copies data to a temporary file before renaming it to the actual bname. Hit
this crash.
But then there was a .t specifically meant to test all rename and unlink
scenarios in sharded volumes.
Then the question is - why didn't the tests @ https://bit.ly/2LScry1 and
https://bit.ly/2vbqO6S cause the process to crash? Well, turns out it's because
of a bug in the script itself where the test cases were supposed to test the
scenario where the dst file doesn't exist but the dst path in both tests was
existent as a remnant of the previous tests and never cleaned up prior to
running these tests.
Need to fix both the bug and the test.
Version-Release number of selected component (if applicable):
Only the master branch
How reproducible:
Every time
Steps to Reproduce:
1. Create any volume with shard enabled.
2. Create a file f1 under the mount point.
3. Rename it to f2.
The mount process crashes.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list