Bug 1070950 - [abrt] obnam: nodestore_disk.py:240:get_node:NodeMissing: Node 0x9 cannot be found in the node store 3951686768651175632: 2: No such file or directory: /mnt/backup/backup/3951686768651175632/nodes/0/0/0/9
Summary: [abrt] obnam: nodestore_disk.py:240:get_node:NodeMissing: Node 0x9 cannot be ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: obnam
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7c713fa41881d2457e3fb46c0ab...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-27 19:33 UTC by Sanne Wouda
Modified: 2015-02-02 10:51 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-02 10:51:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.76 KB, text/plain)
2014-02-27 19:33 UTC, Sanne Wouda
no flags Details
File: dso_list (69 bytes, text/plain)
2014-02-27 19:33 UTC, Sanne Wouda
no flags Details
File: environ (2.34 KB, text/plain)
2014-02-27 19:33 UTC, Sanne Wouda
no flags Details

Description Sanne Wouda 2014-02-27 19:33:34 UTC
Version-Release number of selected component:
obnam-1.6.1-1.fc20

Additional info:
reporter:       libreport-2.1.12
cmdline:        /usr/bin/python /usr/bin/obnam mount -r /mnt/backup/backup --to /mnt/obnam/ --viewmode=multiple
executable:     /usr/bin/obnam
kernel:         3.13.3-201.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
nodestore_disk.py:240:get_node:NodeMissing: Node 0x9 cannot be found in the node store 3951686768651175632: 2: No such file or directory: /mnt/backup/backup/3951686768651175632/nodes/0/0/0/9

Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/fuse.py", line 362, in __call__
    return apply(self.func, args, kw)
  File "/usr/lib64/python2.7/site-packages/obnamlib/plugins/fuse_plugin.py", line 366, in getattr
    return self.get_stat(path)
  File "/usr/lib64/python2.7/site-packages/obnamlib/plugins/fuse_plugin.py", line 237, in get_stat
    metadata = self.get_metadata(path)
  File "/usr/lib64/python2.7/site-packages/obnamlib/plugins/fuse_plugin.py", line 231, in get_metadata
    metadata = self.obnam.repo.get_metadata(*self.get_gen_path(path))
  File "/usr/lib64/python2.7/site-packages/obnamlib/repo.py", line 602, in get_metadata
    encoded = self.client.get_metadata(gen, filename)
  File "/usr/lib64/python2.7/site-packages/obnamlib/clientmetadatatree.py", line 376, in get_metadata
    return tree.lookup(key)
  File "/usr/lib/python2.7/site-packages/larch/tree.py", line 142, in lookup
    node = self._get_node(node[k])
  File "/usr/lib/python2.7/site-packages/larch/tree.py", line 111, in _get_node
    return self.node_store.get_node(node_id)
  File "/usr/lib/python2.7/site-packages/larch/nodestore_disk.py", line 240, in get_node
    raise larch.NodeMissing(self.dirname, node_id, error=e)
NodeMissing: Node 0x9 cannot be found in the node store 3951686768651175632: 2: No such file or directory: /mnt/backup/backup/3951686768651175632/nodes/0/0/0/9

Local variables in innermost frame:
node: None
self: <larch.nodestore_disk.NodeStoreDisk object at 0x13d8750>
node_id: 9
e: IOError(2, 'No such file or directory')
name: '3951686768651175632/nodes/0/0/0/9'

Comment 1 Sanne Wouda 2014-02-27 19:33:39 UTC
Created attachment 868698 [details]
File: backtrace

Comment 2 Sanne Wouda 2014-02-27 19:33:41 UTC
Created attachment 868699 [details]
File: dso_list

Comment 3 Sanne Wouda 2014-02-27 19:33:43 UTC
Created attachment 868700 [details]
File: environ

Comment 4 Michel Lind 2014-12-03 04:50:44 UTC
Hi,

Could you try https://admin.fedoraproject.org/updates/obnam-1.8-1.fc20 and see if that resolves the issue? Thanks!

Comment 5 Sanne Wouda 2015-02-02 10:51:51 UTC
I'm sorry, but I no longer have the backup repository that showed this issue.  Marking as closed.  Feel free to reopen if someone is still experiencing this crash.


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