Arch Linux

inkdinky

Member

Registered: 2011-12-08

Posts: 66

Failed Upgrade due to lack of disk space : Firefox

I have a 4.6G / partition on an old laptop.
I ran pacman -Syu and firefox was one of the packages to be upgraded.
The first couple packages in the upgrade ran fine, but FF being a bit larger encountered a "write failed" due to the size.

[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/libxul.so (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/plugin-container (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/firefox (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/mozilla-xremote-client (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/webapprt-stub (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/defaults/pref/channel-prefs.js (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/webapprt/omni.ja (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/webapprt/webapprt.ini (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/components/components.manifest (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/components/libdbusservice.so (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/components/libmozgnome.so (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/browser/omni.ja (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/browser/chrome.manifest (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/browser/components/ (Can't create '/usr/lib/firefox/browser/components')
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/browser/searchplugins/ (Can't create '/usr/lib/firefox/browser/searchplugins')
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/browser/blocklist.xml (Write failed)
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/browser/extensions/ (Can't create '/usr/lib/firefox/browser/extensions')
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/browser/chrome/ (Can't create '/usr/lib/firefox/browser/chrome')
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/browser/icons/ (Can't create '/usr/lib/firefox/browser/icons')
[2013-05-15 09:34] [ALPM] error: could not extract usr/lib/firefox/browser/defaults/ (Can't create '/usr/lib/firefox/browser/defaults')
[2013-05-15 09:34] [ALPM] error: problem occurred while upgrading firefox
[2013-05-15 09:35] [ALPM-SCRIPTLET] gtk-update-icon-cache: Failed to write hash table
[2013-05-15 09:35] [PACMAN] upgraded firefox (20.0.1-5 -> 21.0-1)

I then did a pacman -Sc to clean out the cache. This usually frees up enough space such that redoing the pacman -Syu will work.
This didn't free any disk space, so I manually went into /var/cache/pacman/pkg and rm'ed some of the larger packages that I wasn't worried about.
I then tried to update, but FF didn't update bc the system appeared to think that FF was updated when it really wasn't.
The system did update the remaining packages in the previous update that weren't updated because the FF update failed.

Trying pacman -S firefox failed with

error: failed to commit transaction (conflicting files)
firefox: /usr/bin/firefox exists in filesystem
firefox: /usr/lib/firefox/application.ini exists in filesystem
firefox: /usr/lib/firefox/browser/blocklist.xml exists in filesystem
firefox: /usr/lib/firefox/browser/chrome.manifest exists in filesystem
firefox: /usr/lib/firefox/browser/omni.ja exists in filesystem
firefox: /usr/lib/firefox/chrome.manifest exists in filesystem
firefox: /usr/lib/firefox/components/components.manifest exists in filesystem
firefox: /usr/lib/firefox/components/libdbusservice.so exists in filesystem
firefox: /usr/lib/firefox/components/libmozgnome.so exists in filesystem
firefox: /usr/lib/firefox/defaults/pref/channel-prefs.js exists in filesystem
firefox: /usr/lib/firefox/dependentlibs.list exists in filesystem
firefox: /usr/lib/firefox/dictionaries exists in filesystem
firefox: /usr/lib/firefox/firefox exists in filesystem
firefox: /usr/lib/firefox/firefox-bin exists in filesystem
firefox: /usr/lib/firefox/hyphenation exists in filesystem
firefox: /usr/lib/firefox/libmozalloc.so exists in filesystem
firefox: /usr/lib/firefox/libxpcom.so exists in filesystem
firefox: /usr/lib/firefox/libxul.so exists in filesystem
firefox: /usr/lib/firefox/mozilla-xremote-client exists in filesystem
firefox: /usr/lib/firefox/omni.ja exists in filesystem
firefox: /usr/lib/firefox/platform.ini exists in filesystem
firefox: /usr/lib/firefox/plugin-container exists in filesystem
firefox: /usr/lib/firefox/removed-files exists in filesystem
firefox: /usr/lib/firefox/run-mozilla.sh exists in filesystem
firefox: /usr/lib/firefox/webapprt-stub exists in filesystem
firefox: /usr/lib/firefox/webapprt/omni.ja exists in filesystem
firefox: /usr/lib/firefox/webapprt/webapprt.ini exists in filesystem
firefox: /usr/share/applications/firefox.desktop exists in filesystem
firefox: /usr/share/icons/hicolor/128x128/apps/firefox.png exists in filesystem
firefox: /usr/share/icons/hicolor/16x16/apps/firefox.png exists in filesystem
firefox: /usr/share/icons/hicolor/210x210/apps/firefox.png exists in filesystem
firefox: /usr/share/icons/hicolor/22x22/apps/firefox.png exists in filesystem
firefox: /usr/share/icons/hicolor/24x24/apps/firefox.png exists in filesystem
firefox: /usr/share/icons/hicolor/256x256/apps/firefox.png exists in filesystem
firefox: /usr/share/icons/hicolor/32x32/apps/firefox.png exists in filesystem
firefox: /usr/share/icons/hicolor/48x48/apps/firefox.png exists in filesystem
firefox: /usr/share/icons/hicolor/64x64/apps/firefox.png exists in filesystem
Errors occurred, no packages were upgraded.

To solve the problem I attempted pacman -R firefox followed by a pacman -S firefox.
FF was removed but I still encountered the same errors when attempting to install FF.

Can I safely go in and rm these files and then re-install FF?

Should I submit a bug request? To me this isn't the desired behavior of the update.
pacman reports in the log that FF was upgraded when in fact it wasn't.

Along the lines of disk space, there is the root reserved 5% on / can I safely make this 0% or is this a big no-no? Do the arguments listed here: http://unix.stackexchange.com/questions … system-why
apply to the / partition as well as the /home partition?

Thanks,
Nick

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: Failed Upgrade due to lack of disk space : Firefox

Can I safely go in and rm these files and then re-install FF?

Generally I mv rather than rm files in this sort of situation. But here I'd say it's pretty obvious those are FF files.

Along the lines of disk space, there is the root reserved 5% on / can I safely make this 0% or is this a big no-no? Do the arguments listed ... apply to the / partition as well as the /home partition?

Pacman runs as root, so I'm pretty sure the reservation has no effect on it.
On a desktop machine with a separate /home, the reservation on / is not such a big deal IMO: regular users shouldn't be doing much writing outside of $HOME. I reserve 1% on / as a failsafe, and have no reservation on /home.

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

inkdinky

Member

Registered: 2011-12-08

Posts: 66

Re: Failed Upgrade due to lack of disk space : Firefox

Simply rm'ing those files and performing the install worked.

Although I sudo pacman, it does respect the 5%, otherwise I wouldn't see this problem.

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: Failed Upgrade due to lack of disk space : Firefox

Although I sudo pacman, it does respect the 5%, otherwise I wouldn't see this problem.

Are you absolutely certain? The space is reserved for root, so anything running as root should not be affected by the reservation.

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

inkdinky

Member

Registered: 2011-12-08

Posts: 66

Re: Failed Upgrade due to lack of disk space : Firefox

I tried to resolve this problem on the irc archlinux pacman channel with no success.
@alphaniner, You're right. The 5% reserve doesn't apply to root/sudo yet I'm not sure what would otherwise cause the write failed error I was seeing.
I just assumed that the lack of unreserved disk space was the cause of the problem.

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

Re: Failed Upgrade due to lack of disk space : Firefox

Do fs check and/or disk check (smartctl).

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

inkdinky

Member

Registered: 2011-12-08

Posts: 66

Re: Failed Upgrade due to lack of disk space : Firefox

Here is the output of
smartctl -a /dev/sda

smartctl 6.1 2013-03-16 r3800 [i686-linux-3.7.5-1-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, [url=http://www.smartmontools.org]www.smartmontools.org[/url]

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Scorpio EIDE
Device Model:     WDC WD400VE-75HDT0
Serial Number:    WD-WXE605102482
Firmware Version: 09.07D09
User Capacity:    40,007,761,920 bytes [40.0 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-6 (minor revision not indicated)
Local Time is:    Wed May 15 17:51:13 2013 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                ( 2400) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        No General Purpose Logging support.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        (  37) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   200   200   051    Pre-fail  Always       -       513
  3 Spin_Up_Time            0x0003   159   155   021    Pre-fail  Always       -       1025
  4 Start_Stop_Count        0x0032   080   080   000    Old_age   Always       -       20623
  5 Reallocated_Sector_Ct   0x0033   199   199   140    Pre-fail  Always       -       1
  7 Seek_Error_Rate         0x000e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   079   079   000    Old_age   Always       -       15910
 10 Spin_Retry_Count        0x0012   100   099   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0012   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   093   093   000    Old_age   Always       -       7353
192 Power-Off_Retract_Count 0x0032   001   001   000    Old_age   Always       -       17344915
193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       17734639
194 Temperature_Celsius     0x0022   108   094   000    Old_age   Always       -       35
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 387 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 387 occurred at disk power-on lifetime: 13598 hours (566 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 04 ab 4b ba e3  Error: UNC 4 sectors at LBA = 0x03ba4bab = 62540715

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 80 2f 4b ba 03 58      00:41:44.840  READ DMA
  ca 00 80 cf eb f9 00 58      00:41:44.840  WRITE DMA
  c8 00 80 4f ea f9 00 58      00:41:44.835  READ DMA
  ca 00 80 4f eb f9 00 58      00:41:44.835  WRITE DMA
  c8 00 80 cf e9 f9 00 58      00:41:44.825  READ DMA

Error 386 occurred at disk power-on lifetime: 13598 hours (566 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  01 51 03 ac 4b ba e3  Error: AMNF 3 sectors at LBA = 0x03ba4bac = 62540716

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 80 2f 4b ba 03 58      00:41:12.115  READ DMA
  ca 00 80 4f ea f9 00 58      00:41:12.115  WRITE DMA
  c8 00 80 2f f7 f9 00 58      00:41:12.115  READ DMA
  ca 00 80 cf e9 f9 00 58      00:41:12.110  WRITE DMA
  c8 00 80 af f6 f9 00 58      00:41:12.110  READ DMA

Error 385 occurred at disk power-on lifetime: 13591 hours (566 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  01 51 03 ac 4b ba e3  Error: AMNF 3 sectors at LBA = 0x03ba4bac = 62540716

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 80 2f 4b ba 03 58      00:26:31.710  READ DMA
  ca 00 80 2f f7 f9 00 58      00:26:31.710  WRITE DMA
  c8 00 80 b7 81 f9 00 58      00:26:31.700  READ DMA
  ca 00 80 af f6 f9 00 58      00:26:31.700  WRITE DMA
  c8 00 80 37 81 f9 00 58      00:26:31.695  READ DMA

Error 384 occurred at disk power-on lifetime: 13564 hours (565 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  01 51 7b ac 4b ba e3  Error: AMNF 123 sectors at LBA = 0x03ba4bac = 62540716

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 80 a7 4b ba 03 58      00:06:55.165  READ DMA
  c8 00 10 7f 4b fc 00 58      00:06:55.150  READ DMA
  ca 00 08 07 f3 60 00 58      00:06:55.145  WRITE DMA
  ca 00 10 7f e6 5e 00 58      00:06:55.145  WRITE DMA
  ca 00 08 27 f1 60 00 58      00:06:55.140  WRITE DMA

Error 383 occurred at disk power-on lifetime: 13564 hours (565 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  01 51 7b ac 4b ba e3  Error: AMNF 123 sectors at LBA = 0x03ba4bac = 62540716

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 80 a7 4b ba 03 58      00:06:52.545  READ DMA
  ca 00 30 4f e6 5e 00 58      00:06:52.545  WRITE DMA
  ca 00 08 af b7 60 00 58      00:06:52.540  WRITE DMA
  ca 00 08 77 b6 60 00 58      00:06:52.540  WRITE DMA
  ca 00 08 bf b5 60 00 58      00:06:52.540  WRITE DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     13883         -
# 2  Short offline       Completed without error       00%         0         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.