Bug 688153 - Yum and Dropbox
Summary: Yum and Dropbox
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 14
Hardware: i386
OS: All
unspecified
unspecified
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-16 13:42 UTC by Scott Weigand
Modified: 2014-01-21 23:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 14:19:29 UTC
Type: ---


Attachments (Terms of Use)

Description Scott Weigand 2011-03-16 13:42:13 UTC
Description of problem:

Cannot remove /var/cache/yum/i386/14/Dropbox/primary.xml.gz.sqlite. I need to remove this file to perform a Yum Clean all and Yum Update. 

Under /var/cache/yum/i386/14/Dropbox/, I have the following output...

ls: cannot access primary.xml.gz.sqlite: Input/output error
total 12
drwxr-xr-x  3 root 4096 Mar 16 09:25 .
drwxr-xr-x. 5 root 4096 Mar 16 09:25 ..
drwxr-xr-x  2 root 4096 Mar  7 13:57 packages
-?????????? ? ?       ?            ? primary.xml.gz.sqlite

Version-Release number of selected component (if applicable):

N/A

How reproducible:

* Install Dropbox, run as a non-root user

* Try to do a Yum Clean All or Yum Update and it will blow up.

Expected results:

Primary.xml.gz.sqlite shouldn't have question marks? 

Additional info:

Yum Clean All output...

yum clean all
Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit
Adding en_US to language list
Cleaning repos: Dropbox fedora updates
Cleaning up Everything
Cannot remove sqlite file /var/cache/yum/i386/14/Dropbox/primary.xml.gz.sqlite
0 delta-package files removed, by presto

Yum Update output...

yum update
Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit
Adding en_US to language list
Determining fastest mirrors
fedora/metalink                                                                                                                       |  22 kB     00:00
updates/metalink                                                                                                                      |  18 kB     00:00
 * fedora: mirror.cogentco.com
 * updates: mirror.cogentco.com
Dropbox                                                                                                                               |  951 B     00:00
Dropbox/primary                                                                                                                       | 1.5 kB     00:00

(process:18615): GLib-CRITICAL **: g_timer_stop: assertion `timer != NULL' failed

(process:18615): GLib-CRITICAL **: g_timer_destroy: assertion `timer != NULL' failed
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 258, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 113, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 392, in doCommands
    self._getTs(needTsRemove)
  File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 99, in _getTs
    self._getTsInfo(remove_only)
  File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 110, in _getTsInfo
    pkgSack = self.pkgSack
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 827, in <lambda>
    pkgSack = property(fget=lambda self: self._getSacks(),
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 617, in _getSacks
    self.repos.populateSack(which=repos)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 283, in populateSack
    sack.populate(repo, mdtype, callback, cacheonly)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in populate
    dobj = repo_cache_function(xml, csum)
  File "/usr/lib/python2.7/site-packages/sqlitecachec.py", line 46, in getPrimary
    self.repoid))
TypeError: Can not open SQL database: unable to open database file

Comment 1 James Antill 2011-03-16 14:19:29 UTC
This is file system corruption, you might be able to work around it by moving the directory somewhere ... but you should reboot and fsck.


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