Bug 50093 - Elm update crashes on out of disk space
Summary: Elm update crashes on out of disk space
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: elm
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-26 19:10 UTC by Alan Cox
Modified: 2007-04-18 16:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-07-31 01:45:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Alan Cox 2001-07-26 19:10:10 UTC
bash-2.04$ elm
Close failed on temp file "/home/anarchy/.elm/mbox.alan.alan"! [No space
left on device]
Discarding any changes made to mail folder ...
Received Segment Violation signal!
Emergency exit taken!
bash-2.04$ df .

Comment 1 Trond Eivind Glomsrxd 2001-07-30 23:04:15 UTC
Can you check if elm-2.5.5-5 fixes the segmantation fault?

Comment 2 Michael Schwendt 2001-07-31 01:38:11 UTC
$ rpm -q elm
elm-2.5.5-5

$ elm
Write failed in copy_message()! [No space left on device]
Emergency exit taken!
Preserving editor composition file "/home/ms/.elm/tmp/snd.21715" ...
Preserving temporary folder "/home/ms/.elm/mbox.ms.ms" ...



Comment 3 Michael Schwendt 2001-07-31 01:42:56 UTC
Steps to reproduce: 

1. export TMPDIR=/some/dir on a partition to be filled up
2. start "elm"
3. fill partition that holds /some/dir, so "df" prints "0"
4. delete a message (marks it a D) and quit


Comment 4 Michael Schwendt 2001-07-31 01:45:02 UTC
Means, SegFault not reproducible at my end. Most likely not an out-of-disk-space
problem.

Comment 5 Trond Eivind Glomsrxd 2001-07-31 04:28:31 UTC
Ok, elm-2.5.5-5 fixes the problem then. Creating more diskspace is a little out
of scope.



Comment 6 Michael Schwendt 2001-07-31 12:15:25 UTC
Though, if there hasn't been a specific fix for anything like this in 2.5.5-5,
this one should be kept an eye on. Alan's case looks like there could be more
involved than just out-of-disk-space.


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