Bug 170379

Summary: RHEL3: losetup (and mount -o loop) wrap at 2GB
Product: Red Hat Enterprise Linux 3 Reporter: Karel Zak <kzak>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED WONTFIX QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: jturner
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: 2006-06-21 10:30:45 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:
Attachments:
Description Flags
patch to fix losetup wrap at 2GB none

Description Karel Zak 2005-10-11 08:17:33 UTC 
+++ This bug was initially created as a clone of Bug #168989 +++

Description of problem:
If you specify an offset value larger than 2GB (2^32) for losetup or mount -o
loop you will not get the expected result (i.e. it will wrap).

-- Additional comment from kzak on 2005-09-21 17:15 EST --
Ah.. good catch. The offset option in losetup in FC3, RHEL3 and RHEL4 is based
on "int" datetype. The problem is fixed in FC4. 

In FC3 it will be fixed in next util-linux update.
Comment 2 Karel Zak 2005-10-20 08:39:25 UTC 
*** Bug 171200 has been marked as a duplicate of this bug. ***
Comment 4 Alex Butcher 2006-02-18 00:37:16 UTC 
Created attachment 124843 [details]
patch to fix losetup wrap at 2GB
Comment 7 Bob Johnson 2006-04-11 15:51:07 UTC 
This issue is on Red Hat Engineering's list of planned work items 
for the upcoming Red Hat Enterprise Linux 3.8 release.  Engineering 
resources have been assigned and barring unforeseen circumstances, Red 
Hat intends to include this item in the 3.8 release.