Bug 224078 - lvm(8) can leave a truncated /etc/lvm/.cache file
lvm(8) can leave a truncated /etc/lvm/.cache file
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: lvm2 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alasdair Kergon
Corey Marthaler
: 224079 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2007-01-23 17:53 EST by Kurtis D. Rader
Modified: 2007-11-16 20:14 EST (History)
6 users (show)

See Also:
Fixed In Version: RHBA-2007-0287
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-07 20:15:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kurtis D. Rader 2007-01-23 17:53:08 EST
The lvm(8) family of commands can leave a truncated /etc/lvm/.cache file if the 
root filesystem becomes full while the file is being written. If the system is 
rebooted at that point it will fail to boot because the subsequent vgscan(8) 
will croak when it attempts to parse the incomplete cache file.

The problem is that the persistent_filter_dump() function does not check the 
return value of any of the writes or fclose(). In fact, simply checking the 
return value of the fclose() and not renaming the temporary file if the close 
fails should be sufficient. This obviously assumes persistent_filter_dump() has 
already been augmented to write to a temporary file and call rename() before 
returning (a change that has already been submitted).
Comment 2 Dave Wysochanski 2007-01-23 20:20:06 EST
*** Bug 224079 has been marked as a duplicate of this bug. ***
Comment 4 Alasdair Kergon 2007-01-26 13:17:54 EST
fclose() check included in lvm2-2.02.20-1.el4

No fwrite() checks yet.
Comment 7 Red Hat Bugzilla 2007-05-07 20:15:42 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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