[tor-dev] tor#16518: Read-Only Filesystem Error opening tor lockfile in 0.2.6.9 but not 0.2.5.12

[aexlfowley at web.de]

Hi devs,

User here. teor send me over from IRC. It's regarding to this
trac-ticket https://trac.torproject.org/projects/tor/ticket/16518
After upgrading from 0.2.5.12 (git-3731dd5c3071dcba) to 0.2.6.9
(git-145b2587d1269af4) an error occured.
I'm on Debian Jessie (stable) on an AMD Athlon 64 X2. Tor won't start
and these are the last lines in log:
[warn] Couldn't open "/media/cRAID/Tor/lock" for locking: Read-only file
system
[err] set_options(): Bug: Acting on config options left us in a broken
state. Dying.

Here's the full log:
http://www.file-upload.net/download-10748122/aexllog.gz.html
Here's also a pastebin of some shell commands I did for the IRC chat:
http://lpaste.net/136099

debug just also contains:
[debug] tor_disable_debugger_attach(): Attemping to disable debugger
attachment to Tor for unprivileged users.
[debug] tor_disable_debugger_attach(): Debugger attachment disabled for
unprivileged users.
[info] tor_lockfile_lock(): Locking "/media/cRAID/Tor/lock"

teor thinks that I "could be experiencing an issue with the tor sandbox
and not getting the right paths
or, tor is running with insufficient permissions"

teor's help and mindfulness was much appreciated.
It lasted about 7 days for me to realize that Tor wasn't running. I'm
now operating 0.2.5.12 successfully, hoping that it's still secure.

Kindest regards