From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: ANNOUNCE: TimeBrowse 0.1 released
Date: Sat, 05 Feb 2011 15:58:12 +0900 (JST) [thread overview]
Message-ID: <20110205.155812.119546877.ryusuke@osrg.net> (raw)
In-Reply-To: <AANLkTinVaRJn4gfj8HousZ3eUhOee3C-U51nMAs6ZLUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sat, 5 Feb 2011 01:48:43 +0900, Ryusuke Konishi wrote:
> - The following error happened when I ran the snapshot manager.
> My python version is 2.7.1+ and yaml version is 3.09
>
> $ sudo ./nilfs2_ss_manager
>
> Traceback (most recent call last):
> File "./nilfs2_ss_manager", line 141, in <module>
> conf = yaml.safe_load(open(conffile))
> File "/usr/lib/python2.7/dist-packages/yaml/__init__.py", line 75,
> in safe_load
> return load(stream, SafeLoader)
> File "/usr/lib/python2.7/dist-packages/yaml/__init__.py", line 58, in load
> return loader.get_single_data()
> File "/usr/lib/python2.7/dist-packages/yaml/constructor.py", line
> 42, in get_single_data
> node = self.get_single_node()
> File "/usr/lib/python2.7/dist-packages/yaml/composer.py", line 39,
> in get_single_node
> if not self.check_event(StreamEndEvent):
> File "/usr/lib/python2.7/dist-packages/yaml/parser.py", line 93, in
> check_event
> self.current_event = self.state()
> File "/usr/lib/python2.7/dist-packages/yaml/parser.py", line 169, in
> parse_document_start
> self.peek_token().start_mark)
> yaml.parser.ParserError: expected '<document start>', but found
> '<block mapping start>'
> in "/etc/nilfs_ss.conf", line 14, column 1
This turned out to be my mistake.
I forgot to comment out the "devices:" line in /etc/nilfs_ss.conf as
below. Sorry.
#devices:
/dev/sda8 : /nilfs
Regards,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-05 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 13:26 ANNOUNCE: TimeBrowse 0.1 released Jiro SEKIBA
[not found] ` <874o8kue08.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2011-02-04 16:48 ` Ryusuke Konishi
[not found] ` <AANLkTinVaRJn4gfj8HousZ3eUhOee3C-U51nMAs6ZLUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-05 6:58 ` Ryusuke Konishi [this message]
2011-02-05 7:11 ` Jiro SEKIBA
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=20110205.155812.119546877.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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