From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Bedup bug report
Date: Wed, 12 Feb 2014 05:46:02 -0800 [thread overview]
Message-ID: <20140212134602.GW27097@merlins.org> (raw)
In-Reply-To: <20140209051936.GF10027@merlins.org>
Does anyone know who the maintainer to send bug reports to, is?
On Sat, Feb 08, 2014 at 09:19:36PM -0800, Marc MERLIN wrote:
> kernel 3.12.7, python 2.7.6-5, debian testing/unstable, bedup installed as per
> pip install --user bedup
>
> I tried installing the git version, but the error is the same:
>
> Anyway, with the other bedup, I get:
> gargamel:/mnt/dshelf2/backup# bedup show
> Traceback (most recent call last):
> File "/usr/local/bin/bedup", line 9, in <module>
> load_entry_point('bedup==0.9.0', 'console_scripts', 'bedup')()
> File "/root/.local/lib/python2.7/site-packages/bedup/__main__.py", line 483, in script_main
> sys.exit(main(sys.argv))
> File "/root/.local/lib/python2.7/site-packages/bedup/__main__.py", line 472, in main
> return args.action(args)
> File "/root/.local/lib/python2.7/site-packages/bedup/__main__.py", line 70, in cmd_show_vols
> sess = get_session(args)
> File "/root/.local/lib/python2.7/site-packages/bedup/__main__.py", line 105, in get_session
> upgrade_schema(engine, database_exists)
> File "/root/.local/lib/python2.7/site-packages/bedup/migrations.py", line 38, in upgrade_schema
> context = MigrationContext.configure(engine.connect())
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1678, in connect
> return self._connection_cls(self, **kwargs)
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 59, in __init__
> self.__connection = connection or engine.raw_connection()
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1747, in raw_connection
> return self.pool.unique_connection()
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/pool.py", line 272, in unique_connection
> return _ConnectionFairy._checkout(self)
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/pool.py", line 608, in _checkout
> fairy = _ConnectionRecord.checkout(pool)
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/pool.py", line 425, in checkout
> rec = pool._do_get()
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/pool.py", line 838, in _do_get
> c = self._create_connection()
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/pool.py", line 277, in _create_connection
> return _ConnectionRecord(self)
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/pool.py", line 402, in __init__
> pool.dispatch.connect(self.connection, self)
> File "/root/.local/lib/python2.7/site-packages/sqlalchemy/event/attr.py", line 247, in __call__
> fn(*args, **kw)
> File "/root/.local/lib/python2.7/site-packages/bedup/__main__.py", line 89, in sql_setup
> assert val == ('wal',), val
> AssertionError: (u'delete',)
>
> gargamel:/mnt/dshelf2/backup# bedup dedup --db-path dedup --defrag .
> also fails the same way
>
> Last thing that happens is
> open("/usr/lib/python2.7/lib-tk/_sqlite3module.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
> open("/usr/lib/python2.7/lib-tk/_sqlite3.py", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
> open("/usr/lib/python2.7/lib-tk/_sqlite3.pyc", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
> stat64("/usr/lib/python2.7/lib-dynload/_sqlite3", 0xff921890) = -1 ENOENT (No such file or directory)
> open("/usr/lib/python2.7/lib-dynload/_sqlite3.i386-linux-gnu.so", O_RDONLY|O_LARGEFILE) = 5
> open("/usr/lib/python2.7/lib-dynload/_sqlite3.i386-linux-gnu.so", O_RDONLY|O_CLOEXEC) = 6
> open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 6
> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
> open("/usr/lib/libsqlite3.so.0", O_RDONLY|O_CLOEXEC) = 6
> getcwd("/mnt/dshelf2/backup", 1024) = 20
> stat64("/mnt/dshelf2/backup/dedup", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> open("/mnt/dshelf2/backup/dedup", O_RDWR|O_CREAT|O_LARGEFILE, 0644) = 3
> Traceback (most recent call last):
> File "/usr/local/bin/bedup", line 9, in <module>
> open("/usr/local/bin/bedup", O_RDONLY|O_LARGEFILE) = 4
> load_entry_point('bedup==0.9.0', 'console_scripts', 'bedup')()
> File "/root/.local/lib/python2.7/site-packages/bedup-0.9.0-py2.7-linux-x86_64.egg/bedup/__main__.py", line 487, in script_main
> (...)
>
> Any suggestions?
>
> Thanks,
> Marc
> --
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
> Microsoft is to operating systems ....
> .... what McDonalds is to gourmet cooking
> Home page: http://marc.merlins.org/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-02-12 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 5:19 Bedup bug report Marc MERLIN
2014-02-12 13:46 ` Marc MERLIN [this message]
2014-02-12 14:33 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140212134602.GW27097@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).