Re: upgrade from wheezy to jessie
On 01/06/2015 06:57 AM, Joe wrote: > On Tue, 06 Jan 2015 13:42:43 + > Eduardo M KALINOWSKI wrote: > >> On Ter, 06 Jan 2015, Joe wrote: >>> The main issue is that anything local mounted in /etc/fstab (even >>> removable drives) will be treated as essential, and if they are not >>> there, boot will fail. The answer is either to remove any such >>> drives from fstab, as the kernel automounting should be good enough >>> now to do the job consistently, or to mark them as not being >>> required for boot. >> >> This is already noted in the release notes. >> > > Yes, but I believe it is likely to be the main reason for a possible > lack of booting, about which the OP was concerned. I was making the > point that is a very simple thing to avoid. > I very recently updated two systems from wheezy to jessie. Both are running fine (I'm using one right now), but I had exactly the problem above on one system. I had an fstab entry that halted booting. Removed that line and it booted fine. The only other issue I've had since the upgrade is a wireless driver (which I didn't want) was failing to load and my logs filled up 89G of space telling me over and over in messages, syslog and kern.log until the root partition was full. -Thom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54ac0450.5070...@cagroups.com
Re: An experiment in backup
On 01/16/2015 01:28 AM, Joel Roth wrote: > On Thu, Jan 15, 2015 at 09:32:24PM -0800, Kevin O'Gorman wrote: >> I care because I like to have a lot of free space in my partitions, but I >> hate to use backup time and space on the holes. > > Hi Kevin, > > If you copy the whole partition, byte-for-byte, as with the > 'dd' command, you copy everything, including the free space. > > If you copy via the filesystem, e.g. using rsync, you just > pay for what you use, and all the files are immediately > available. Restoring a file is a matter of > copying. > > ... > > #!/bin/sh > RSYNC="rsync -avx " > CMD="$RSYNC \ > --exclude /dev \ > --exclude /proc \ > --exclude /sys \ > --exclude /home \ > --exclude /tmp \ > --exclude /var/cache/apt/archives \ > --exclude /var/run \ > / /mnt/$1/root" > echo $CMD >> /var/log/backup.log > I can confirm that the above works. I recently used rsync to copy my live system to another partition, excluding /dev /proc /sys /tmp and /home. After setting grub to boot the new partition, it works fine. I'm using it now. -Thom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b8edd7.40...@cagroups.com
Re: An experiment in backup
On 01/17/2015 09:29 AM, Kevin O'Gorman wrote: > Did you have to re-create any of the excluded directories before it would > boot properly? > > This looks a lot like what I do already, but is not working for me. I'll > check the details. > Kevin, you sent this directly to me, not the list. I have /home on another partition, so I just mounted that in the new system. I created blank /tmp /dev /proc and /sys. They are populated at boot time. Just match the permissions from the system you're copying from. I have not tried backing up a live system using tar. Just using rsync to copy file by file. A quick google search just brought up this link: https://wiki.archlinux.org/index.php/full_system_backup_with_rsync which is very similar to how I did it. -Thom > > On Fri, Jan 16, 2015 at 2:54 AM, Thom Miller wrote: > >> >> >> On 01/16/2015 01:28 AM, Joel Roth wrote: >>> On Thu, Jan 15, 2015 at 09:32:24PM -0800, Kevin O'Gorman wrote: >>>> I care because I like to have a lot of free space in my partitions, but >> I >>>> hate to use backup time and space on the holes. >>> >>> Hi Kevin, >>> >>> If you copy the whole partition, byte-for-byte, as with the >>> 'dd' command, you copy everything, including the free space. >>> >>> If you copy via the filesystem, e.g. using rsync, you just >>> pay for what you use, and all the files are immediately >>> available. Restoring a file is a matter of >>> copying. >>> >>> ... >>> >>> #!/bin/sh >>> RSYNC="rsync -avx " >>> CMD="$RSYNC \ >>> --exclude /dev \ >>> --exclude /proc \ >>> --exclude /sys \ >>> --exclude /home \ >>> --exclude /tmp \ >>> --exclude /var/cache/apt/archives \ >>> --exclude /var/run \ >>> / /mnt/$1/root" >>> echo $CMD >> /var/log/backup.log >>> >> I can confirm that the above works. I recently used rsync to copy my >> live system to another partition, excluding /dev /proc /sys /tmp and /home. >> >> After setting grub to boot the new partition, it works fine. I'm using >> it now. >> >> -Thom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54baf14a.1020...@cagroups.com
