tly greyed out.
I have had a couple of corrupted tree logs recently and had to use
btrfs-zero-log (mentioned in an earlier thread). Otherwise returning to
2.6.38 is the workaround.
~mck
--
"A mind that has been stretched will never return to it's original
dimension." Albert Einstein
|
cussed in future threads, eg "Btrfs slowdown".
dumbing out fsync (libeatmydata) only gives marginal improvements...
~mck
--
Bombing for peace is like F***ing for virginity | www.semb.wever.org |
www.sesat.no | tech.finn.no | http://xss-http-filter.sf.net
signature.asc
Description:
p://ubuntuforums.org/archive/index.php/t-1103926.html ?
I don't know of the consequences... but it would prove your theory?
~mck
--
“Don’t worry about people stealing your ideas. If your ideas are any
good, you’ll have to ram them down people’s throats.” - Howard Aiken
| http://semb.wever.org
I didn't try mounting after the btrfs-zero-log so i don't
know if it or btrfs-select-super was actually the cure.
Knowing very little about zero-log and select-super should i continue
using my laptop like normal now?
Or is this filesystem still considered corrupt and i should bac
en
to try.
I do have a btrfs-image i can upload if it's of any help...
~mck
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
