On 7 February 2016 at 20:27, Lionel Bouton <lionel-subscription@xxxxxxxxxxx> wrote: > Hi, > > Le 07/02/2016 14:15, Andreas Hild a écrit : >> Dear All, >> >> The file system on a RAID1 Debian server seems corrupted in a major >> way, with 99% of the files not found. This was the result of a >> precarious shutdown after a crash that was preceded by an accidental >> misconfiguration in /etc/fstab; it pointed "/" and "/tmp" to one and >> the same UUID by omitting a subvol entry. >> >> Is there any way to repair or recover a substantial part of this RAID? > > I don't think the RAID is damaged: most distributions including Debian > remove nearly all files from /tmp at boot. > If /tmp and / were as you described the same filesystem your server most > probably did what amounts to "rm -rf /". You would probably have got the > same result with any filesystem as mounting the same filesystem at > several points in the VFS is not BTRFS-specific. > > Unless you can restore a snapshot or there is a way to debug the > filesystem to restore a previous state, I'm afraid there's nothing to be > done. Thank you for the fast response! I see. Just to be certain here, I have noted a vast difference between the output of the "regular" 'df' and 'btrfs fi df'. Regular df shows about 85MB of data on this file system, whereas btrfs fi df shows the expected 168.00GiB (the exact amount of data that was there). What does this mean? Best wishes, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
