Note you could have used snapshot to recover the files if they were on / (root). Also sda2 is root and sda3 is home. Where were you trying to recover??? And why would you give a colleague access to your important files ??
On 2015-05-19 14:06, gogalthorp wrote:
>
> Note you could have used snapshot to recover the files if they were on /
> (root). Also sda2 is root and sda3 is home. Where were you trying to
> recover??? And why would you give a colleague access to your important
> files ??
The information is incomplete, but photorec I doubt very much that it
supports btrfs. My assumption is that he tried to recover files from
another disk, perhaps a usb stick. Photorec saves what it finds to a
different media, and he selected root, so it filled up with what it
found. He should have selected home.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
>
> Greetings guys. Need help here.
>
> So the story is I installed PhotoRec to recover a file my colleague
> deleted.
>
> On the selection sda part, I’m not sure which folder to recover hence i
> blindly chose 1.
>
> Next thing i know the KDE crashed, with only black screen.
>
> Did some googling and it turns out i don’t have enough space on /root or
> /home to run KDE.
>
> inserted this command df -h and this shows;
>
> [image: http://s12.postimg.org/jimf6kfcd/IMG_20150519_180705.jpg]
>
> Please advise what is my next step as im noob to opensuse.
>
>
Have you tried removing some snapshots using “snapper”, can be found in
Yast, I had exactly the same prob yesterday and so deleted all snapshots and
de-installed ( a bit drastic I know and not really wise ) but I don`t need
it here.
I go nearly half of my / partition back
HTH
–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum
“PhotoRec ignores the file system and goes after the underlying data, so it will still
work even if your media’s file system has been severely damaged or reformatted.” http://www.cgsecurity.org/wiki/PhotoRec
>
> “PhotoRec ignores the file system and goes after the underlying data, so
> it will still
> work even if your media’s file system has been severely damaged or
> reformatted.”
> http://www.cgsecurity.org/wiki/PhotoRec
I know, so they claim. But btrfs is special.
> By default PhotoRec searches for many file types and the recovered data
> could take up a lot of space.
It only works more or less right with photos and some other multimedia
files.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2015-05-19 14:27, Baskitcaise wrote:
> Have you tried removing some snapshots using “snapper”, can be found in
> Yast, I had exactly the same prob yesterday and so deleted all snapshots and
> de-installed ( a bit drastic I know and not really wise ) but I don`t need
> it here.
He copied a lot of files. I doubt that the snapshots make a lot of
difference in his case.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Looks like what ever you did “recover” went to root filling it up. Without haveing looked over you shoulder at the time you did it I have no idea what you did.
As mentioned BTRFS is special and photrec may not understand it to write to it properly?? Who knows???
I’d first try zapping the snapshots they do take up room and that may give you the edge you need to start KDE. But it is not the solution. You have to find where those files you recovered went and either delete them or move them to home somewhere
Note you must use the snapper tool to actually remove the snapshots. man snapper should give you some clues
On 2015-05-19 17:06, thivaakar wrote:
> i was trying to recover an excel file on /home/somewheressomwhere.
If you were trying to recover a file from the /home filesystem, and it
was mounted, your chances of recovering something are close to nil. Very
possibly the space was reused and overwritten.
> He copied a lot of files. I doubt that the snapshots make a lot of
> difference in his case.
>
I agree Carlos but it might give him enough space to get the system up and
running in KDE to make it easier for him to see what is what if he is not
comfortable in the CLI.
Cheers.
–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum
On 2015-05-19 17:59, Baskitcaise wrote:
> Carlos E. R. donned his tin foil hat and penned:
>
>
>> He copied a lot of files. I doubt that the snapshots make a lot of
>> difference in his case.
>>
>
> I agree Carlos but it might give him enough space to get the system up and
> running in KDE to make it easier for him to see what is what if he is not
> comfortable in the CLI.
On 2015-05-21 11:26, thivaakar wrote:
>
> robin_listas;2710803 Wrote:
>>> now which folder may i clear? im not familiar with some of these
>> files.
>>
>> Well, paste here the output of “ls /”, inside a code tags block (’#’
>> button)
> Code:
> --------------------
> BOOMGROW:~ # ls /
> .readahead Shan boot etc home lib64 opt root sbin share1 sys usr
> .snapshots bin dev ftp lib mnt proc run selinux srv tmp var
>
>
> --------------------
>
>
> here you go bro. what’s next?
I do not know… I do not see an obvious directory where the photorec
output would go.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
/proc
Check if it has a lot of lovely numbered directories with one that has a root inside of it… I’m just guessing but that will be there, with /proc right there for you as well… with a lot of numbered directories inside… want to guess what one of those has inside it self? Same number as before no doubt…
Essentially, that’s where all your free space went - in my case 30G snarled up in there.
ls /proc/1/root/proc/1/root/proc/1/root/proc/1/root/proc/1/root/proc/1/root…
you get the drift…
