FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have just upgraded to Fedora 18 using FedUp, but I find most of my files lost after the upgrading.
My home directory uses btrfs, and the files lost are all that recently not used.
Is this a bug of btrfs or something else? Anybody can help me to restore the files?
Thanks in advance.
I find most of my files lost after the upgrading My home directory uses btrfs, and the files lost are all that recently not used. Is this a bug of btrfs or something else?
I doubt that has anything to do with btrfs and even if I would post-upgrade first check logs that FedUp, Anaconda, Yum and syslog provide for any clues before actually using the system again.
it seems the same problem, though my file system is btrfs(but not encrypted)
I failed to upgrade using the network (2+ times), then used the ISO option, it just upgraded some of my packages(even though the iso do have some of them). After all, it can boot, though has no desktop. I did the installing, upgrading and cleaning manually.
Quote:
Originally Posted by unSpawn
I doubt that has anything to do with btrfs and even if I would post-upgrade first check logs that FedUp, Anaconda, Yum and syslog provide for any clues before actually using the system again.
You did make a backup, right?
That's the problem!!! NO... Orz..
I use "du -sh"
find the space is in using, but only directories can be found. I think the files are not lost, but just don't know how to get them back.
I failed to upgrade using the network (2+ times), then used the ISO option, it just upgraded some of my packages(even though the iso do have some of them). After all, it can boot, though has no desktop. I did the installing, upgrading and cleaning manually.
It would be good to mention such details in your original post. It may not mean much to you, after all you're already in this mess and you only want to find a way out of it, but for us it's important to know. FedUp should, just like the former Fedora installer "Anaconda", log information to either log files in /var/log, /tmp or /root. So if there's trouble that doesn't show up on stdout then it would be good to check /tmp and /root for any installer or upgrade log files and see if /var/log/yum.log and /var/log/messages hold clues.
Quote:
Originally Posted by was4444
Orz
Just chalk it up as a lesson to learn from.
Quote:
Originally Posted by was4444
I use "du -sh" find the space is in using, but only directories can be found. I think the files are not lost, but just don't know how to get them back.
Boot your Spherical Cow (runlevel may be rescue, doesn't matter) run the following commands. Explanation: first become root, then show current kernel version, show which Fedora release is installed, see what mount points are defined in /etc/fstab, then show which physical devices are mounted, finally show how much each home users directory on disk holds". Number each line for readability and pipe output to a file.
Code:
sudo su -l;
( uname -r; cat /etc/system-release; grep -v ^# /etc/fstab|grep .; mount|grep "v/[h|s]d"; find /home/* -maxdepth 0 -type d -print0|xargs -0 -iD du --apparent-size -hs 'D' ) | nl | tee /tmp/output.txt
Please review then -=attach=- the plain text file "/tmp/output.txt".
It would be good to mention such details in your original post. It may not mean much to you, after all you're already in this mess and you only want to find a way out of it, but for us it's important to know. FedUp should, just like the former Fedora installer "Anaconda", log information to either log files in /var/log, /tmp or /root. So if there's trouble that doesn't show up on stdout then it would be good to check /tmp and /root for any installer or upgrade log files and see if /var/log/yum.log and /var/log/messages hold clues.
Here is the what I have done all:
1. as my /var doesn't have enough spaces, I made a symbolic link in the /home partions( ln -s /home/tmp /var/tmp ); before upgrading, it works, but in upgrading, it doesn't. maybe that's problem why I cannot upgrade from the network.
2. Then I download the ISO files and use fedup's iso option. It begins to install package after reboot. it stoped at a process of installing or something else(sorry for forgetting this) it seems like something about"link".
3. Then I boot in command line, do some installing, cleaning. I have to use startx to use the desktop environment even now.
I read /root/fredupdebug.log, /var/log/upgrade.log yum.log and message, but didn't find anything useful for at least me. Since I use tmpfs for /tmp, nothing left every reboot. I will attach some of them.
Quote:
Originally Posted by unSpawn
Just chalk it up as a lesson to learn from.
a lesson of blood...
Quote:
Originally Posted by unSpawn
Boot your Spherical Cow (runlevel may be rescue, doesn't matter) run the following commands. Explanation: first become root, then show current kernel version, show which Fedora release is installed, see what mount points are defined in /etc/fstab, then show which physical devices are mounted, finally show how much each home users directory on disk holds". Number each line for readability and pipe output to a file.
Code:
sudo su -l;
( uname -r; cat /etc/system-release; grep -v ^# /etc/fstab|grep .; mount|grep "v/[h|s]d"; find /home/* -maxdepth 0 -type d -print0|xargs -0 -iD du --apparent-size -hs 'D' ) | nl | tee /tmp/output.txt
Please review then -=attach=- the plain text file "/tmp/output.txt".
Thanks for the nfo. While you didn't exactly run the command like I wanted to it does show /home indeed uses btrfs and that /home/cuckoo holds about 16G worth of data. Wrt "Is this a bug of btrfs or something else?" your upgrade.log is remarkably free of errors related to btrfs. Here is a list of all Fedora btrfs-related open tickets: https://bugzilla.redhat.com/buglist....uery_based_on= sorted by ticket number. While I haven't seen any bug there related to your problem maybe you can spot one. Wrt "most of my files lost after the upgrading" try to come up with some examples please. Can be partial file names or directory names and then try using 'find'. Say for example that you're looking for a file name containing "Deimos" in your home directory you could:
Code:
find /home/cuckoo -type f -iname "*deimos*" -ls
or if it's a file called "Phobos" in your firefox profile directory:
Code:
find /home/cuckoo/.mozilla/firefox -type f -iname "*phobos*" -ls
You get the idea. After you've located those files try to check their specs in the File Manager to verify you can access them. If there's files you can't access by either find or File Manager please elaborate.
Thanks for the nfo. While you didn't exactly run the command like I wanted to it does show /home indeed uses btrfs and that /home/cuckoo holds about 16G worth of data.
it seems that I lost a bracket, then remove the other one.
Quote:
Originally Posted by unSpawn
Wrt "Is this a bug of btrfs or something else?" your upgrade.log is remarkably free of errors related to btrfs. Here is a list of all Fedora btrfs-related open tickets: https://bugzilla.redhat.com/buglist....uery_based_on= sorted by ticket number. While I haven't seen any bug there related to your problem maybe you can spot one. Wrt "most of my files lost after the upgrading"
maybe that's not a bug of btrfs, for, as you can see, my /var and /usr are both btrfs, and don't lose anything, right? the difference is that I make a link, and use the /home to store the packages that fedup downloads. and the hard disk of my laptop may also be a problem, for there are some bad blocks(my laptop really has a history). maybe btrfs+fedup+bad blocks results to lost files.
Quote:
Originally Posted by unSpawn
try to come up with some examples please.
the files lost are all that have not accessed recently(say about 1+ weeks ago), including configure files, documents, videos, musics and so on. left only the directories that contain them. but the files recently used don't get lost.
here is a example,( I use: find . * -ls > find.txt) find.txt
I find that the spaces in using are not the lost files, but the big ISO files downloaded, I forgot that. This time, maybe the files are really lost.
maybe that's not a bug of btrfs, for, as you can see, my /var and /usr are both btrfs, and don't lose anything, right?
Not that I've seen any evidence of that but if you say so.
Quote:
Originally Posted by was4444
the difference is that I make a link, and use the /home to store the packages that fedup downloads.
You made a symbolic link from directory /var/tmp to /home/tmp. If you think btrfs somehow didn't honor the concept of directories then you're supposed to run diagnostics on it and file a bug report.
Quote:
Originally Posted by was4444
and the hard disk of my laptop may also be a problem, for there are some bad blocks(my laptop really has a history). maybe btrfs+fedup+bad blocks results to lost files.
Your laptop has known malfunctions, it didn't meet the requirements for upgrading and you decided to skip making backups. Then you went ahead with the upgrade and now you wonder what's gone wrong?... Saying "my laptop really has a history" doesn't quite cover it ;-p
Quote:
Originally Posted by was4444
the files lost are all that have not accessed recently(say about 1+ weeks ago), including configure files, documents, videos, musics and so on. left only the directories that contain them. but the files recently used don't get lost. here is a example,( I use: find . * -ls > find.txt) I find that the spaces in using are not the lost files, but the big ISO files downloaded, I forgot that.
You didn't use my example, you showed 'find' results that don't include files you talk about and you didn't confirm /home/cuckoo actually holds 16GB of data. That means there's nothing left I can help you with, sorry.
Quote:
Originally Posted by was4444
This time, maybe the files are really lost.
One final thing to do is boot a Live CD that contains the latest version of Testdisk and Photorec, run testdisk as 'testdisk /debug /log /dev/sda3', explore the file system and check if that allows you to see your "documents, videos, musics and so on" you somehow (again, no evidence) can't see from within Fedora. If there's files you should save recover them to a separate medium like and external USB disk or stick or minimally another mounted partition. That's all I can come up with. Good luck!
Not that I've seen any evidence of that but if you say so.
You made a symbolic link from directory /var/tmp to /home/tmp. If you think btrfs somehow didn't honor the concept of directories then you're supposed to run diagnostics on it and file a bug report.
Your laptop has known malfunctions, it didn't meet the requirements for upgrading and you decided to skip making backups. Then you went ahead with the upgrade and now you wonder what's gone wrong?... Saying "my laptop really has a history" doesn't quite cover it ;-p
Though the upgrading before works well, that not a excuse. I will take the lesson, do make a backup now.
Quote:
Originally Posted by unSpawn
You didn't use my example, you showed 'find' results that don't include files you talk about and you didn't confirm /home/cuckoo actually holds 16GB of data. That means there's nothing left I can help you with, sorry.
I know, the info is too little for sth. I try the command above, but nothing in the standout. my example can just show that there are a lot of folds with nothing in them.
Quote:
Originally Posted by unSpawn
One final thing to do is boot a Live CD that contains the latest version of Testdisk and Photorec, run testdisk as 'testdisk /debug /log /dev/sda3', explore the file system and check if that allows you to see your "documents, videos, musics and so on" you somehow (again, no evidence) can't see from within Fedora. If there's files you should save recover them to a separate medium like and external USB disk or stick or minimally another mounted partition. That's all I can come up with. Good luck!
I will try it, if find sth useful, I will post here. Thank you!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.