Marc MERLIN wrote (ao):
That said, it's working fine again for now after I went back to kernel 3.5.3
(down from 3.6.3). It hasn't been long enough to say for sure, but there is
a remote possibility that changes in 3.6 actually caused my drive to freeze
after several hours of use.
When that
On Thu, Nov 01, 2012 at 11:56:18AM +0100, Sander wrote:
For now, I'll stick with 3.5.3 for a while to make sure my drive is actually
ok (it seems to be afterall), and once I'm happy that it's the case, I'll go
back to 3.6.3 with serial console remote logging and try to capture the full
Marc MERLIN wrote (ao):
What happened is that my SSD is craping out and failing to write after
a certain number of uptime hours.
What model ssd is that if I may ask?
Sander
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to
On Wed, Oct 31, 2012 at 10:24:40AM +0100, Sander wrote:
Marc MERLIN wrote (ao):
What happened is that my SSD is craping out and failing to write after
a certain number of uptime hours.
What model ssd is that if I may ask?
I had my first one, Crucial C300 just die with all my data about 3
On Mon, Oct 29, 2012 at 10:48:02AM -0700, Marc MERLIN wrote:
Then, I figured, I'd try mounting all the active snapshots one per one,
and they worked:
After that, I was able to mount the root (volid 0) without a crash and
my filesystem looks fine again.
Ok, I was wrong.
What happened is that
Hi,
Thanks for the reply and hints.
On Sun, Oct 28, 2012 at 11:05:42PM -0600, Chris Murphy wrote:
I also have hourly, daily, weekly
btrfs subvolume snapshots, but I can't use those currently since I can't
mount the base filesystem.
It might be worth unmounting it. Then only remounting
First, I used another tool to see how the FS looked like, and maybe in
the hopes of having a list of subvolumes without mounting it:
gandalfthegreat:~# btrfs-calc-size /dev/mapper/bootdsk
Calculating size of root tree
180.00KB total size, 0.00 inline data, 1 nodes, 44 leaves, 2 levels
On Thu, Oct 25, 2012 at 01:12:23PM -0700, Marc MERLIN wrote:
On Thu, Oct 25, 2012 at 02:03:49PM -0600, cwillu wrote:
3) Want me to try btrfsck although it may make it impossible for me to
reproduce the bug and test a fix, as well as potentially break the
filesystem
more (last time I
On Oct 25, 2012, at 2:12 PM, Marc MERLIN m...@merlins.org wrote:
I also have hourly, daily, weekly
btrfs subvolume snapshots, but I can't use those currently since I can't
mount the base filesystem.
It might be worth unmounting it. Then only remounting a snapshot well before
the problem
If any devs want info out of my drive, please ask today, I really need to
fix it tomorrow.
I'll try btrfs-zero-log otherwise and if not, wipe and start over.
Marc
On Thu, Oct 25, 2012 at 12:58:05PM -0700, Marc MERLIN wrote:
Howdy,
I can wait a day or maybe 2 before I have to wipe and restore
Howdy,
I can wait a day or maybe 2 before I have to wipe and restore from backup.
Please let me know if you have a patch against 3.6.3 you'd like me to try
to mount/recover this filesystem, or whether you'd like me to try btrfsck.
My laptop had a problem with its boot drive which prevented
On Thu, Oct 25, 2012 at 1:58 PM, Marc MERLIN m...@merlins.org wrote:
Howdy,
I can wait a day or maybe 2 before I have to wipe and restore from backup.
Please let me know if you have a patch against 3.6.3 you'd like me to try
to mount/recover this filesystem, or whether you'd like me to try
On Thu, Oct 25, 2012 at 02:03:49PM -0600, cwillu wrote:
3) Want me to try btrfsck although it may make it impossible for me to
reproduce the bug and test a fix, as well as potentially break the
filesystem
more (last time I tried btrfsck, it outputted thousands of lines and never
13 matches
Mail list logo
