I was able to recover the filesystem using the btrfsck from git (Btrfs
v0.20-rc1-358-g194aa4a) .
I encourage btrfsck to output a line similar to Errors found. Run
again with --repair to attempt repairs. when errors are found.
From using other fsck tools, I expected repairs to be attempted unless
Should I interpret the different used amounts (902.01GB vs 902.03GB)
on my recovered RAID1 filesystem as that not all data is actually
mirrored and so I should run a balance? The devices in the filesystem
below are the same make/model drives.
# btrfs fi show
Label: 'mcmedia' uuid:
On Thu, Jul 18, 2013 at 11:11:03AM -0400, Sandy McArthur wrote:
Should I interpret the different used amounts (902.01GB vs 902.03GB)
on my recovered RAID1 filesystem as that not all data is actually
mirrored and so I should run a balance? The devices in the filesystem
below are the same
On Thu, Jul 18, 2013 at 04:21:28PM +0100, Hugo Mills wrote:
On Thu, Jul 18, 2013 at 11:11:03AM -0400, Sandy McArthur wrote:
Should I interpret the different used amounts (902.01GB vs 902.03GB)
on my recovered RAID1 filesystem as that not all data is actually
mirrored and so I should run a
I have a btrfs filesystem that is corrupt so that I cannot remove a
few files. Attempting to delete these temp files from before a crash
leaves the filesystem read-only and sends a trace to the syslog.
Assistance correcting this issue is most appreciated.
I have two disks /dev/sd{b,c}1 to make up
Sandy McArthur posted on Wed, 17 Jul 2013 10:06:05 -0400 as excerpted:
have a btrfs filesystem that is corrupt so that I cannot remove a few
files. Attempting to delete these temp files from before a crash leaves
the filesystem read-only and sends a trace to the syslog. Assistance
correcting
