Jesse Emeth posted on Sun, 30 Dec 2018 16:58:12 +0800 as excerpted:
> Hi Duncan
>
> The backup is irrelevant in this case. I have a backup of this
> particular problem.
> I've had BTRFS on my OS system blow up several times.
> There are several snapshots of this within the subvolume.
> However, s
2018 23:22:46 +0100 as
> > excerpted:
> >
> >> Hello all,
> >> Is it possible to undelete files on BTRFS ? I just deleted a bunch of
> >> folders and would like to restore them if possible.
> >>
> >> I found this script
> >> https://gist
Duncan posted on Sun, 30 Dec 2018 04:11:20 + as excerpted:
> Adrian Bastholm posted on Sat, 29 Dec 2018 23:22:46 +0100 as excerpted:
>
>> Hello all,
>> Is it possible to undelete files on BTRFS ? I just deleted a bunch of
>> folders and would like to restore them if
Adrian Bastholm posted on Sat, 29 Dec 2018 23:22:46 +0100 as excerpted:
> Hello all,
> Is it possible to undelete files on BTRFS ? I just deleted a bunch of
> folders and would like to restore them if possible.
>
> I found this script
> https://gist.github.com/Changaco/45f8d1
Hello all,
Is it possible to undelete files on BTRFS ? I just deleted a bunch of
folders and would like to restore them if possible.
I found this script
https://gist.github.com/Changaco/45f8d171027ea2655d74 but it's not
finding stuff ..
./btrfs-undelete /dev/sde1 ./foto /home/st
Hello,
I had a similar issue. On OpenSuse I deleted /.snapshots/ and was not aware that
/.snapshots/1/snapshot/ is the default subvolume representing my root file
system.
So I had no snapshot left, all ro subvolumes have been deleted before, and the
default subvolume had big parts deleted before I
I have a disk with a database directory that was cleared accidentally.
This disk stay mounted for 3 days but I don't see any writing on it
after the deletion. The disk was almost full when the deletion occurred.
However, trying to use btrfs-undelete give me no results. :
# sudo btrfs-undelete
On Mon, Sep 01, 2014 at 08:00:03PM +0300, Konstantinos Skarlatos wrote:
> On 1/9/2014 7:27 μμ, Marc MERLIN wrote:
> >On Sat, Aug 30, 2014 at 11:26:52AM -1000, Jean-Denis Girard wrote:
> >>So I commented out the break on line 238 of btrfs-find-root so that it
> >Thanks for that report.
> >Can a deve
On Mon, Sep 01, 2014 at 06:08:28PM -1000, Jean-Denis Girard wrote:
> Le 01/09/2014 07:00, Konstantinos Skarlatos a écrit :
> > Until then, can we make this into a concise set of instructions so we
> > can post it on the wiki?
>
> I would be happy to contribute to the wiki, but I'm not sure where t
Le 01/09/2014 07:00, Konstantinos Skarlatos a écrit :
> Until then, can we make this into a concise set of instructions so we
> can post it on the wiki?
I would be happy to contribute to the wiki, but I'm not sure where to
add this: a new paragraph in the "Problem FAQ" or a new page?
Thanks,
Jea
On 1/9/2014 7:27 μμ, Marc MERLIN wrote:
On Sat, Aug 30, 2014 at 11:26:52AM -1000, Jean-Denis Girard wrote:
So I commented out the break on line 238 of btrfs-find-root so that it
Thanks for that report.
Can a developer review this and see if it should be made an option or
removed entirely?
I thi
On Sat, Aug 30, 2014 at 11:26:52AM -1000, Jean-Denis Girard wrote:
> So I commented out the break on line 238 of btrfs-find-root so that it
Thanks for that report.
Can a developer review this and see if it should be made an option or
removed entirely?
Marc
> continues even if it thinks it went p
So I commented out the break on line 238 of btrfs-find-root so that it
continues even if it thinks it went past the fs size, rerun the command,
and I finally got a list of blocks to try!
Then as you suggested I did:
for i in `awk '{print $3}' root.txt`
do echo " $i --
Le 28/08/2014 21:40, Konstantinos Skarlatos a écrit :
> On 28/8/2014 8:04 μμ, Jean-Denis Girard wrote:
>> Hi Chris,
>>
>> Thanks for your detailed answer.
>>
>> Le 28/08/2014 06:25, Chris Murphy a écrit :
>>> 9. btrfs-find-root /dev/sdc
>>> Super think's the tree root is at 29917184, chunk root 209
On 28/8/2014 8:04 μμ, Jean-Denis Girard wrote:
Hi Chris,
Thanks for your detailed answer.
Le 28/08/2014 06:25, Chris Murphy a écrit :
9. btrfs-find-root /dev/sdc
Super think's the tree root is at 29917184, chunk root 20987904
Well block 4194304 seems great, but generation doesn't match, have=2
Le 28/08/2014 11:51, Chris Murphy a écrit :
> Ahh yes. So you'll see here that there's a new build for you not yet in
> updates repo.
btrfs-progs-3.16-1.fc20.x86_64 installed, but it doesn't change anything:
[jdg@tiare tmp]$ btrfs-find-root x220_home.img
Super think's the tree root is at 1152308
On Aug 27, 2014, at 12:04 PM, Jean-Denis Girard wrote:
> I'm on Fedora 20, with kernel 3.15.10-200.fc20.x86_64, and
> btrfs-progs-3.14.2-3.fc20.x86_64.
Ahh yes. So you'll see here that there's a new build for you not yet in updates
repo.
http://koji.fedoraproject.org/koji/buildinfo?buildID=57
On Aug 28, 2014, at 3:23 PM, Jean-Denis Girard wrote:
> So this seems fine; why is btrfs-find-root not working for me?
Don't know. btrfs-progs 3.16 is current in
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git master
branch. It's already built since yesterday in koji for
On Aug 28, 2014, at 11:04 AM, Jean-Denis Girard wrote:
> Hi Chris,
>
> Thanks for your detailed answer.
>
> Le 28/08/2014 06:25, Chris Murphy a écrit :
>> 9. btrfs-find-root /dev/sdc
>> Super think's the tree root is at 29917184, chunk root 20987904
>> Well block 4194304 seems great, but gener
Le 28/08/2014 10:21, Chris Murphy a écrit :
> What do you get for
[root@x220 ~]# btrfs-debug-tree -R /dev/mapper/home
root tree: 115230801920 level 1
chunk tree: 131072 level 1
extent tree key (EXTENT_TREE ROOT_ITEM 0) 115230806016 level 2
device tree key (DEV_TREE ROOT_ITEM 0) 115191881728 leve
On Aug 28, 2014, at 11:04 AM, Jean-Denis Girard wrote:
> Hi Chris,
>
> Thanks for your detailed answer.
>
> Le 28/08/2014 06:25, Chris Murphy a écrit :
>> 9. btrfs-find-root /dev/sdc
>> Super think's the tree root is at 29917184, chunk root 20987904
>> Well block 4194304 seems great, but gener
Hi Chris,
Thanks for your detailed answer.
Le 28/08/2014 06:25, Chris Murphy a écrit :
> 9. btrfs-find-root /dev/sdc
> Super think's the tree root is at 29917184, chunk root 20987904
> Well block 4194304 seems great, but generation doesn't match, have=2, want=9
> level 0
> Well block 4243456 see
Line 84
"$dir/restore" -i -t $id -m "$regex" "$dev" $out
I don't see a -m option for btrfs restore, maybe use --path-regex instead.
I just did this without the script and it worked:
1. mkfs.btrfs /dev/sdc
2. mount /dev/sdc /mnt
3. mkdir /mnt/pics
4. scp IMG_3327.tif :/mnt/pics/
Jean-Denis Girard posted on Wed, 27 Aug 2014 08:04:34 -1000 as excerpted:
> Two days ago I mistakenly deleted a directory on a btrfs file system. As
> soon as I realized, I cleanly unmounted the partition, and have not
> touched it since then. I have no snapshot and no backup; I was on
> vacations
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi list,
Two days ago I mistakenly deleted a directory on a btrfs file system. As
soon as I realized, I cleanly unmounted the partition, and have not
touched it since then. I have no snapshot and no backup; I was on
vacations with my laptop, and the d
25 matches
Mail list logo
