Bug 682597

Summary: fedora on USB flash drive is broken on update
Product: [Fedora] Fedora Reporter: Account closed by user <c719711>
Component: device-mapperAssignee: Orphan Owner <extras-orphan>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: agk, bmarzins, dcantrell, dwysocha, extras-orphan, heinzm, jonathan, mbroz, prockai
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-02 10:19:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
call trace - top
none
call trace - half left
none
call trace - half right
none
call trace - half bottom none

Description Account closed by user 2011-03-07 00:39:36 UTC 
- put Fedora-14-i686-Live-Desktop.iso in a USB flash drive with liveusb-creator-3.9.3-1.fc14.noarch
- boot from it
- yum -y update
- wait, wait, ...
- crash

[...]
rpmdb: fsync: Input/output error
rpmdb: fsync: Input/output error
[...]

tested with 2 different usb devices:

- OCZ_Rally2_Turbo 4G http://www.ocztechnology.com/ocz-rally2-turbo-usb-2-0-flash-drive-eol.html

- Pico_C 8G http://www.supertalent.com/products/stt_usb_detail.php?type=Pico

something wrong in any file system squash, ext4 ...
Comment 1 Account closed by user 2011-03-07 18:13:02 UTC 
 
Upper test was done in a ACER Aspire M1640(workstation).

Redone on a Lenovo ThinkPad T61(laptop) with OCZ_Rally2_Turbo 4G. And it is broken again.

photos attached.
Comment 2 Account closed by user 2011-03-07 18:19:44 UTC 
Created attachment 482759 [details]
call trace - top
Comment 3 Account closed by user 2011-03-07 18:21:59 UTC 
Created attachment 482760 [details]
call trace - half left
Comment 4 Account closed by user 2011-03-07 18:24:15 UTC 
Created attachment 482761 [details]
call trace - half right
Comment 5 Account closed by user 2011-03-07 18:25:59 UTC 
Created attachment 482762 [details]
call trace - half bottom
Comment 6 Brian Lane 2011-04-11 16:49:55 UTC 
The livecd isn't meant to be updated like this. It uses an overlay system to handle file changes. When this overlay runs out of space it fails and doesn't handle that gracefully. I am not sure if there is anything that we can do to avoid this, but I'll reassign to device-mapper and see what they say.

Either way, I wouldn't expect to be able to run yum update on a live system.
Comment 7 Account closed by user 2011-05-18 00:19:33 UTC 
(In reply to comment #6)

> The livecd isn't meant to be updated like this. It uses an overlay system to
> handle file changes. When this overlay runs out of space it fails and doesn't
> handle that gracefully. I am not sure if there is anything that we can do to
> avoid this, but I'll reassign to device-mapper and see what they say.
> 
> Either way, I wouldn't expect to be able to run yum update on a live system.

I did the test again, this time with a USB-hard_drive and the underlying fs was EXT4 instead vfat. And ALL went OK..

space on /, aka /dev/mapper/live-rw, was never full.