On Mon, Jul 01, 2013 at 11:56:30PM +0100, Peter Chant wrote:
Sirs,
my recently slowing file system is now going read only after trying
a defrag or other operation. I'm wondering whether this is the
result of a hardware failure or a btrfs or some other issue. Output
of dmesg:
[snip]
[
On 07/02/2013 08:29 AM, Hugo Mills wrote:
This is usually an indication that you have bad hardware -- I'd
suggest testing RAM, PSU, CPU in that order. I'm not sure what, if
anything, can be done to fix the error on the disk right now.
Thanks, appreciated.
Hmm. I've got one stick of ram out
On Tue, Jul 02, 2013 at 06:36:48PM +0100, Peter Chant wrote:
On 07/02/2013 08:29 AM, Hugo Mills wrote:
This is usually an indication that you have bad hardware -- I'd
suggest testing RAM, PSU, CPU in that order. I'm not sure what, if
anything, can be done to fix the error on the disk right
On 07/02/2013 06:48 PM, Hugo Mills wrote:
So the damage probably happened then, if that stick is bad.
Filesystems have this irritating habit of remembering things done to
them across reboots. :) Hugo.
The previous action to the defrag was to delete 48 hours worth of
hourly snapshots. I was
Sirs,
my recently slowing file system is now going read only after trying a
defrag or other operation. I'm wondering whether this is the result of
a hardware failure or a btrfs or some other issue. Output of dmesg:
127.750401] DR0: DR1: DR2:
