Bug 765363 (GLUSTER-3631) - zero byte files when perl search and replace script
Summary: zero byte files when perl search and replace script
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3631
Product: GlusterFS
Classification: Community
Component: quick-read
Version: 3.2.3
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
: 800381 (view as bug list)
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2011-09-26 07:21 UTC by Anush Shetty
Modified: 2015-12-01 16:45 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 18:03:55 UTC
Regression: RTA
Mount Type: fuse
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Anush Shetty 2011-09-26 07:21:58 UTC 
Reported on a user mailing list. When perl search and replace string command is used, it created zero byte files. Happens only when executed manually but works fine when executed within a script.

This issue is not seen with quick-read disabled.



echo 'test' > dot

perl -i -pe 's/test/somethingelse/' dot

ls -lh dot
-rw-r--r-- 1 root root 0 2011-09-26 11:43 dot
Comment 1 Raghavendra G 2011-11-11 01:30:07 UTC 
Patch sent, waiting for it to be pulled in.
Comment 2 Amar Tumballi 2011-12-08 07:39:47 UTC 
please work on review comments and resubmit.
Comment 3 Anand Avati 2012-03-28 17:40:48 UTC 
CHANGE: http://review.gluster.com/506 (performance/quick-read: make unlink aware of open-behind behaviour of quick-read.) merged in master by Vijay Bellur (vijay)
Comment 4 Anand Avati 2012-03-29 06:02:58 UTC 
CHANGE: http://review.gluster.com/3028 (performance/quick-read: fix build errors.) merged in master by Vijay Bellur (vijay)
Comment 5 shishir gowda 2012-03-29 07:21:41 UTC 
*** Bug 800381 has been marked as a duplicate of this bug. ***
Comment 6 Anush Shetty 2012-03-29 12:27:11 UTC 
Verified in the mainline [fbfb4d48491b160436e6ac986057a8fe5e320502]
Note You need to log in before you can comment on or make changes to this bug.