From: Amedee Van Gasse <amedee@vangasse.eu>
To: linux-btrfs@vger.kernel.org
Cc: hugo@carfax.org.uk
Subject: Re: Announcing btrfs-gui
Date: Sat, 12 Nov 2011 01:24:57 +0100 [thread overview]
Message-ID: <4EBDBCD9.8060009@vangasse.eu> (raw)
In-Reply-To: <20110601232058.GA22619@carfax.org.uk>
On 02-06-11 01:20, Hugo Mills wrote:
*snip*
> Like all silly ideas, this one got a bit out of hand, and seems to
> have turned into something vaguely useful. I'm therefore pleased to
> announce the first major public release of btrfs-gui[1]: a point-and-
> click tool for managing btrfs filesystems.
>
> The tool currently can scan for and list btrfs filesystems and the
> volumes they live on. It can show the allocation and usage of data in
> a selected filesystem, categorised by use, replication, and device. It
> can show and manipulate subvolumes and snapshots: creation, deletion,
> and setting the default. For those with servers to manage, it also has
> the ability to ssh into a remote machine, and manage its filesystems
> remotely (so you don't have to have X installed on your servers just
> to use btrfs-gui on them).
*snip*
> Unless the traffic gets too high-volume, or unless someone
> important objects, I'm going to suggest that bug reports should go to
> this list for now (cc'd me, if you like). Note that this isn't an
> "offical" btrfs project -- it's just something I knocked together on
> my own.
I seem to have stumbled upon a bug.
During install, Ubuntu gives the user the option to use btrfs as the
root filesystem. It automatically creates two subvolumes, @ (for /) and
@home (for /home, only if no other partition is used for /home), like this:
mount | grep btrfs
/dev/sda6 on / type btrfs (rw,subvol=@)
/dev/sda6 on /home type btrfs (rw,subvol=@home)
/dev/sda6 on
/tmp/btrfs-gui-kl6zx1/12624/eba4f1e9-5b55-4e14-abb8-5a3cf3625c56 type
btrfs (rw,subvolid=0)
When gtrfs-gui scans for filesystems, it gives the error
Root helper exception: b'@' is not JSON serializable
This is the relevant console output:
Helper: found label None, UUID eba4f1e9-5b55-4e14-abb8-5a3cf3625c56
Helper: found dev 1 = /dev/sda6
Helper: Created private directory /tmp/btrfs-gui-kl6zx1
Helper: Mounted filesystem UUID=eba4f1e9-5b55-4e14-abb8-5a3cf3625c56 at
/tmp/btrfs-gui-kl6zx1/12624/eba4f1e9-5b55-4e14-abb8-5a3cf3625c56
Traceback (most recent call last):
File "/usr/local/lib/python3.2/dist-packages/btrfsgui/hlp/helper.py",
line 40, in main
COMMANDS[command](parameters)
File "/usr/local/lib/python3.2/dist-packages/btrfsgui/hlp/subvol.py",
line 126, in sv_list
sys.stdout.write(json.dumps(res))
File "/usr/lib/python3.2/json/__init__.py", line 224, in dumps
return _default_encoder.encode(obj)
File "/usr/lib/python3.2/json/encoder.py", line 188, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib/python3.2/json/encoder.py", line 246, in iterencode
return _iterencode(o, 0)
File "/usr/lib/python3.2/json/encoder.py", line 170, in default
raise TypeError(repr(o) + " is not JSON serializable")
TypeError: b'@' is not JSON serializable
Kind regards,
Amedee Van Gasse
amedee@vangasse.eu
next prev parent reply other threads:[~2011-11-12 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 23:20 Announcing btrfs-gui Hugo Mills
2011-06-02 8:31 ` Fajar A. Nugraha
2011-06-02 8:41 ` Hugo Mills
2011-06-03 21:48 ` Hugo Mills
2011-06-06 15:40 ` Chris Mason
2011-11-12 0:24 ` Amedee Van Gasse [this message]
2011-11-23 12:33 ` Hugo Mills
2011-11-23 17:39 ` cwillu
2011-11-18 15:50 ` Phillip Susi
2011-11-23 1:12 ` [PATCH 0/3] Show Chunks by position Phillip Susi
2011-11-23 12:34 ` Hugo Mills
2011-11-23 1:12 ` [PATCH 1/3] Changed volume_df() to return all chunks with their offsets Phillip Susi
2011-11-23 1:12 ` [PATCH 2/3] Update UsageDisplay to be capable of displaying all chunks by position Phillip Susi
2011-11-23 1:13 ` [PATCH 3/3] Add radio knob to show space by position or combined Phillip Susi
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=4EBDBCD9.8060009@vangasse.eu \
--to=amedee@vangasse.eu \
--cc=hugo@carfax.org.uk \
--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).