Re: Emergency - Can't Boot
On Saturday 30 July, 2011 13:46:21 Hugo Mills wrote: On Sat, Jul 30, 2011 at 12:51:51PM -0700, . wrote: I just did my monthly dist-upgrade and rebooted, only to have it stall at Control D. It tried to automatically run fsck.btrfs and of course it failed, and insists that I run it manually. I can't. I've rebooted several times and can't get past Control D. Don't know where it keeps track of the number of reboots since last fsck. What do you do in a case like this? [Just a note -- this seems to have been fixed in a conversation on IRC, by linking /bin/true to /bin/fsck.btrfs] Yes that fixed it. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Emergency - Can't Boot
On Saturday 30 July, 2011 19:34:26 Fajar A. Nugraha wrote: IMHO a better fix is to just disable fsck on fstab for that fs. Something like # file system mount point type options dump pass LABEL=ROOT / btrfs subvolid=258,compress-force=lzo,noatime0 0 I've done that too. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Kernel Modules
Just compiled a custom kernel, but unable to mount a btrfs partition. It essentially says 'unrecognized filesystem'. What could be missing? # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_EXT4_FS=y CONFIG_EXT4_FS_XATTR=y # CONFIG_EXT4_FS_POSIX_ACL is not set # CONFIG_EXT4_FS_SECURITY is not set # CONFIG_EXT4_DEBUG is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_JBD2=y # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set CONFIG_JFS_FS=y # CONFIG_JFS_POSIX_ACL is not set # CONFIG_JFS_SECURITY is not set # CONFIG_JFS_DEBUG is not set # CONFIG_JFS_STATISTICS is not set # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set CONFIG_BTRFS_FS=y CONFIG_BTRFS_FS_POSIX_ACL=y # CONFIG_NILFS2_FS is not set CONFIG_FS_POSIX_ACL=y CONFIG_FILE_LOCKING=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_FANOTIFY is not set CONFIG_QUOTA=y CONFIG_QUOTA_NETLINK_INTERFACE=y CONFIG_PRINT_QUOTA_WARNING=y # CONFIG_QUOTA_DEBUG is not set CONFIG_QUOTA_TREE=m # CONFIG_QFMT_V1 is not set CONFIG_QFMT_V2=m CONFIG_QUOTACTL=y CONFIG_QUOTACTL_COMPAT=y CONFIG_AUTOFS4_FS=y CONFIG_FUSE_FS=y CONFIG_CUSE=y CONFIG_GENERIC_ACL=y -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Kernel Modules
On Saturday 9 July, 2011 10:12:43 you wrote: If your btrfs lives on two or more devices you will have to run 'btrfs device scan' prior to mount or give all devices as arguments to mount.btrfs. Ohhh, I'd added a disk drive without modifying fstab. Thanks. Where would you put a device scan to happen at boot? On another subject, I guess there are two ways to remove old snapshot directories: - btrfs subvolume delete - rm -rf I understand that snapshots are cumulative for files and do not duplicate, but is it necessary to use the subvolume delete command to preserve the integrity of remaining snapshots? And also, about once a week KDE locks up on me after a suspend, and I have to power-cycle it. Is there any maintenance I should do on a btrfs part when this happens? -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Thursday 5 May, 2011 23:33:33 Sander wrote: Can you do: echo true /var/lib/dpkg/info/grub-installer.postinst and try again? At some point somehow grup-pc apparently got installed, even with the script failure. So I tried my dist-upgrade again, and seems to have completed almost 400 packages, but three still fail: Errors were encountered while processing: linux-image-2.6.38-2-amd64 grub-pc linux-image-2.6-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) I can't reboot at this point, as on this machine I started a 'balance' through ssh on another machine, and it's been running for over 12 hours. It does not respond to ^C and I'm afraid to reboot with it running. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Friday 6 May, 2011 05:20:28 Sander wrote: Can you post the error? # apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Setting up linux-image-2.6.38-2-amd64 (2.6.38-3) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.38-2-amd64 initrd.img(/boot/initrd.img-2.6.38-2-amd64 ) points to /boot/initrd.img-2.6.38-2-amd64 (/boot/initrd.img-2.6.38-2-amd64) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.38-2-amd64.postinst line 348, STDIN line 7. vmlinuz(/boot/vmlinuz-2.6.38-2-amd64 ) points to /boot/vmlinuz-2.6.38-2-amd64 (/boot/vmlinuz-2.6.38-2-amd64) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.38-2-amd64.postinst line 348, STDIN line 7. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 2.6.38-2-amd64 /boot/vmlinuz-2.6.38-2-amd64 dkms: running auto installation service for kernel 2.6.38-2-amd64: vboxhost (3.2.12)...failed. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.38-2-amd64 /boot/vmlinuz-2.6.38-2-amd64 run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.38-2-amd64 /boot/vmlinuz-2.6.38-2-amd64 run-parts: executing /etc/kernel/postinst.d/update-notifier 2.6.38-2-amd64 /boot/vmlinuz-2.6.38-2-amd64 run-parts: executing /etc/kernel/postinst.d/zz-update-grub 2.6.38-2-amd64 /boot/vmlinuz-2.6.38-2-amd64 /usr/sbin/grub-probe: error: cannot stat `/dev/root'. run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.38-2-amd64.postinst line 801, STDIN line 7. dpkg: error processing linux-image-2.6.38-2-amd64 (--configure): subprocess installed post-installation script returned error exit status 9 configured to not write apport reports Setting up grub-pc (1.99~rc1-13) ... grub-probe: error: cannot stat `/dev/root'. Installation finished. No error reported. /usr/sbin/grub-probe: error: cannot stat `/dev/root'. dpkg: error processing grub-pc (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports dpkg: dependency problems prevent configuration of linux-image-2.6-amd64: linux-image-2.6-amd64 depends on linux-image-2.6.38-2-amd64; however: Package linux-image-2.6.38-2-amd64 is not configured yet. dpkg: error processing linux-image-2.6-amd64 (--configure): dependency problems - leaving unconfigured configured to not write apport reports Errors were encountered while processing: linux-image-2.6.38-2-amd64 grub-pc linux-image-2.6-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
Same old problem. On Friday 6 May, 2011 06:21:58 Sander wrote: Can you try: dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb apt-get dist-upgrade # dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb (Reading database ... 135273 files and directories currently installed.) Preparing to replace grub-pc 1.99~rc1-13 (using .../grub-pc_1.99~rc1-13_amd64.deb) ... Unpacking replacement grub-pc ... Setting up grub-pc (1.99~rc1-13) ... grub-probe: error: cannot stat `/dev/root'. Installation finished. No error reported. /usr/sbin/grub-probe: error: cannot stat `/dev/root'. dpkg: error processing grub-pc (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: grub-pc # If that (second step) doesn't work: echo true /var/lib/dpkg/info/grub-installer.postinst apt-get dist-upgrade # echo true /var/lib/dpkg/info/grub-installer.postinst # dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb (Reading database ... 135273 files and directories currently installed.) Preparing to replace grub-pc 1.99~rc1-13 (using .../grub-pc_1.99~rc1-13_amd64.deb) ... Unpacking replacement grub-pc ... Setting up grub-pc (1.99~rc1-13) ... grub-probe: error: cannot stat `/dev/root'. Installation finished. No error reported. /usr/sbin/grub-probe: error: cannot stat `/dev/root'. dpkg: error processing grub-pc (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: grub-pc # which update-grub /usr/sbin/update-grub # /usr/sbin/update-grub -v grub-mkconfig (GRUB) 1.99~rc1-13 Apparently 1.99~rc1-13 is installed and synaptic confirms this, despite the script failure, although every .mod file in /usr/lib/grub is in the i386-pc directory. I'm running 64bit Debian Testing with kernel 2.6.37-2. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Friday 6 May, 2011 07:17:00 you wrote: Hm. Just do cp /bin/true /usr/sbin/grub-probe Yikes, it came up with an ncurses screen saying: GRUB failed to install to the following devices: │ │ │ │ /dev/sda │ │ │ │ Do you want to continue anyway? If you do, your computer may not start up properly. │ │ │ │ Writing GRUB to boot device failed - continue? │ │ │ │Yes No │ │ Say No and another ncurses screen saying: The grub-pc package is being upgraded. This menu allows you to select which devices│ │ you'd like grub-install to be automatically run for, if any. │ │ │ │ Running grub-install automatically is recommended in most situations, to prevent the │ │ installed GRUB core image from getting out of sync with GRUB modules or grub.cfg. │ │ │ │ If you're unsure which drive is designated as boot drive by your BIOS, it is often a │ │ good idea to install GRUB to all of them. │ │ │ │ Note: it is possible to install GRUB to partition boot records as well, and some │ │ appropriate partitions are offered here. However, this forces GRUB to use the │ │ blocklist mechanism, which makes it less reliable, and therefore is not recommended. │ │ │ │ GRUB install devices: │ │ │ │[*] /dev/sda (750156 MB; WDC_WD7500BPKT-00PK4T0) │ │ │ │ │ │ Ok So I canceled out of it, not knowing WTH. I don't understand why the newer grub still doesn't understand BTRFS? # cp /bin/true /usr/sbin/grub-probe # dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb (Reading database ... 135273 files and directories currently installed.) Preparing to replace grub-pc 1.99~rc1-13 (using .../grub-pc_1.99~rc1-13_amd64.deb) ... Unpacking replacement grub-pc ... Setting up grub-pc (1.99~rc1-13) ... Auto-detection of a filesystem of failed. Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org ^[Auto-detection of a filesystem of failed. Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org Auto-detection of a filesystem of failed. Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-2.6.38-2-amd64 Found initrd image: /boot/initrd.img-2.6.38-2-amd64 Found linux image: /boot/vmlinuz-2.6.37-2 Found Windows XP Pro on /dev/sda4 done Processing triggers for man-db ... #/usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub # -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Friday 6 May, 2011 07:58:47 you wrote: Say 'yes', try to finish your upgrade. Now when I ran it, it went as normal for some reason. Then: grub-install /dev/sda Auto-detection of a filesystem of failed. Please report this together with the output of /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub to bug-g...@gnu.org update-grub Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-2.6.38-2-amd64 Found initrd image: /boot/initrd.img-2.6.38-2-amd64 Found linux image: /boot/vmlinuz-2.6.37-2 Found Windows XP Pro on /dev/sda4 done I'm afraid to reboot though, because yesterday I started a btrfs fi balance on this machine while sshed to another, and that is still running 15 hours later with no indication of progress nor sign of abating. ^C is ineffective. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Friday 6 May, 2011 08:15:25 cac...@quantum-sci.com wrote: I'm afraid to reboot though, because yesterday I started a btrfs fi balance on this machine while sshed to another, and that is still running 15 hours later with no indication of progress nor sign of abating. ^C is ineffective. Wow. I was very nearly completely screwed. I went ahead and rebooted, but grub.cfg was not set up at all. I had no way to run update-grub on that root, and so tried manually filling in the missing parameters. That didn't work, probably through the obfuscation of UUIDs I couldn't determine what was really going on. What a terrible idea the way they were implemented, UUIDs. Why not put the current device assignment somewhere in the number? Terrible. I ended up copying an old grub.cfg from a backup, and that got me at least booted, though with lots of grub errors. Now I am at a loss. I don't understand this. grub-update at least -pretended- to work before I rebooted. I am still in shock. MUST get some actual work done today, rather than bit-twiddling. MUST try and make a living. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
Anyone here? On Friday 6 May, 2011 10:09:29 cac...@quantum-sci.com wrote: On Friday 6 May, 2011 08:15:25 cac...@quantum-sci.com wrote: I'm afraid to reboot though, because yesterday I started a btrfs fi balance on this machine while sshed to another, and that is still running 15 hours later with no indication of progress nor sign of abating. ^C is ineffective. Wow. I was very nearly completely screwed. I went ahead and rebooted, but grub.cfg was not set up at all. I had no way to run update-grub on that root, and so tried manually filling in the missing parameters. That didn't work, probably through the obfuscation of UUIDs I couldn't determine what was really going on. What a terrible idea the way they were implemented, UUIDs. Why not put the current device assignment somewhere in the number? Terrible. I ended up copying an old grub.cfg from a backup, and that got me at least booted, though with lots of grub errors. Now I am at a loss. I don't understand this. grub-update at least -pretended- to work before I rebooted. I am still in shock. MUST get some actual work done today, rather than bit-twiddling. MUST try and make a living. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Friday 6 May, 2011 13:51:37 Peter Stuge wrote: cac...@quantum-sci.com wrote: I don't understand this. Clearly. Please continue the discussion in a debian or grub forum.. It really has nothing to do with btrfs. No thanks. This is a BTRFS problem, and if you people don't want to face it, that's fine. I'm tearing out BTRFS and using another filesystem. And rest assured, I'm warning others too. That's enough. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Wednesday 4 May, 2011 02:51:54 Sander wrote: Put an exit on top of /etc/kernel/postrm.d/zz-update-grub and try again. Install grub-pc 1.99~rc1-13 from Sid. First I put an exit right after #! /bin/sh and it failed. Then I moved /etc/kernel/postrm.d/zz-update-grub to / and it still failed. Grub is not running as a daemon, so I shouldn't have to reboot for the new version to take effect. And frankly at the moment I'm afraid to reboot, with only grub-common installed. # dpkg -i /var/cache/apt/archives/grub-common_1.99~rc1-13_amd64.deb (Reading database ... 136689 files and directories currently installed.) Preparing to replace grub-common 1.98+20100804-14 (using .../grub-common_1.99~rc1-13_amd64.deb) ... Unpacking replacement grub-common ... Setting up grub-common (1.99~rc1-13) ... Installing new version of config file /etc/grub.d/10_linux ... Installing new version of config file /etc/grub.d/30_os-prober ... Installing new version of config file /etc/grub.d/00_header ... Installing new version of config file /etc/grub.d/20_linux_xen ... Processing triggers for install-info ... Processing triggers for man-db ... # dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb (Reading database ... 136703 files and directories currently installed.) Preparing to replace grub-pc 1.99~rc1-13 (using .../grub-pc_1.99~rc1-13_amd64.deb) ... Unpacking replacement grub-pc ... Setting up grub-pc (1.99~rc1-13) ... grub-probe: error: cannot stat `/dev/root'. Installation finished. No error reported. /usr/sbin/grub-probe: error: cannot stat `/dev/root'. dpkg: error processing grub-pc (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: grub-pc -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
Anyone have a suggestion? Also on another machine set up similarly, I now cannot mkdir. It says 'no space left on device'. df says: # df /dev/sdb Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb 3907029168 2658010524 1246486516 69% /home sdb and sdc are one btrfs 'raid' volume. What could be wrong? On Thursday 5 May, 2011 07:49:09 cac...@quantum-sci.com wrote: On Wednesday 4 May, 2011 02:51:54 Sander wrote: Put an exit on top of /etc/kernel/postrm.d/zz-update-grub and try again. Install grub-pc 1.99~rc1-13 from Sid. First I put an exit right after #! /bin/sh and it failed. Then I moved /etc/kernel/postrm.d/zz-update-grub to / and it still failed. Grub is not running as a daemon, so I shouldn't have to reboot for the new version to take effect. And frankly at the moment I'm afraid to reboot, with only grub-common installed. # dpkg -i /var/cache/apt/archives/grub-common_1.99~rc1-13_amd64.deb (Reading database ... 136689 files and directories currently installed.) Preparing to replace grub-common 1.98+20100804-14 (using .../grub-common_1.99~rc1-13_amd64.deb) ... Unpacking replacement grub-common ... Setting up grub-common (1.99~rc1-13) ... Installing new version of config file /etc/grub.d/10_linux ... Installing new version of config file /etc/grub.d/30_os-prober ... Installing new version of config file /etc/grub.d/00_header ... Installing new version of config file /etc/grub.d/20_linux_xen ... Processing triggers for install-info ... Processing triggers for man-db ... # dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb (Reading database ... 136703 files and directories currently installed.) Preparing to replace grub-pc 1.99~rc1-13 (using .../grub-pc_1.99~rc1-13_amd64.deb) ... Unpacking replacement grub-pc ... Setting up grub-pc (1.99~rc1-13) ... grub-probe: error: cannot stat `/dev/root'. Installation finished. No error reported. /usr/sbin/grub-probe: error: cannot stat `/dev/root'. dpkg: error processing grub-pc (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db ... Errors were encountered while processing: grub-pc -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
I was afraid of this finger-pointing. Of course no one at Debian is going to know how to fix BTRFS jamming the package management system. That's ridiculous. It's starting to look like BTRFS is just busted in Debian, and I'll have to reinstall everything over a different filesystem. I hate to give up btrfs raid and snapshotting, but these failures are just unlivable. Is Oracle aware of this? I'll have to warn others in the various forums that BTRFS breaks Debian, because no one warned me. This is unlivable, not to mention unbelievable. On Thursday 5 May, 2011 12:28:19 cwillu wrote: You'll need to contact somebody more familiar with debian, as this isn't really a btrfs issue. Yes, btrfs is the obvious cause, but it's grub's handling of it that is the problem, and dpkg's handling of grub's failure that is really blocking you. This is what it meant by does debian support btrfs?. It's not a question of whether btrfs is in debian's kernel, but whether all the pieces of debian which are directly or indirectly affected by btrfs are known to work right, and whether they're currently willing to spend effort on these issues. If they're not currently providing that level of support, then it's completely up to you to have a good understanding of how the rest of debian is put together so that you yourself can make things works. As was mentioned previously, there is an updated grub package, so your main objective is to find out from debian how to disable or override the failing package long enough to install the replacement. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
Here is the relevant section of strace:
-
chmod(/etc/grub.d/05_debian_theme.dpkg-new, 0755) = 0
unlink(/etc/grub.d/05_debian_theme.dpkg-new) = 0
stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0
write(6, 2011-05-05 13:21:57 status unpac..., 56) = 56
write(4, Package: grub-pc\nStatus: install..., 1795) = 1795
ftruncate(4, 1795) = 0
fsync(4)= 0
close(4)= 0
munmap(0x7f32f849, 4096)= 0
rename(/var/lib/dpkg/updates/tmp.i, /var/lib/dpkg/updates/0011) = 0
open(/var/lib/dpkg/updates/, O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 4
fsync(4)= 0
close(4)= 0
open(/var/lib/dpkg/updates/tmp.i, O_WRONLY|O_CREAT|O_TRUNC, 0666) = 4
fcntl(4, F_GETFD) = 0
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fstat(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f32f849
write(4, #padding\n#padding\n#padding\n#padd..., 4096) = 4096
write(4, padding\n#padding\n#padding\n#paddi..., 512) = 512
lseek(4, 0, SEEK_SET) = 0
stat(/etc/localtime, {st_mode=S_IFREG|0644, st_size=2819, ...}) = 0
write(6, 2011-05-05 13:21:58 status half-..., 63) = 63
write(4, Package: grub-pc\nStatus: install..., 1802) = 1802
ftruncate(4, 1802) = 0
fsync(4)= 0
close(4)= 0
munmap(0x7f32f849, 4096)= 0
rename(/var/lib/dpkg/updates/tmp.i, /var/lib/dpkg/updates/0012) = 0
open(/var/lib/dpkg/updates/, O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 4
fsync(4)= 0
close(4)= 0
open(/var/lib/dpkg/updates/tmp.i, O_WRONLY|O_CREAT|O_TRUNC, 0666) = 4
fcntl(4, F_GETFD) = 0
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fstat(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f32f849
write(4, #padding\n#padding\n#padding\n#padd..., 4096) = 4096
write(4, padding\n#padding\n#padding\n#paddi..., 512) = 512
lseek(4, 0, SEEK_SET) = 0
stat(/var/lib/dpkg/info/grub-pc.postinst, {st_mode=S_IFREG|0755,
st_size=23003, ...}) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7f32f8475a70) = 29950
rt_sigaction(SIGQUIT, {SIG_IGN, [], SA_RESTORER, 0x7f32f7d281e0}, {SIG_DFL, [],
SA_RESTORER, 0x7f32f7d281e0}, 8) = 0
rt_sigaction(SIGINT, {SIG_IGN, [], SA_RESTORER, 0x7f32f7d281e0}, {SIG_DFL, [],
SA_RESTORER, 0x7f32f7d281e0}, 8) = 0
wait4(29950, grub-probe: error: cannot stat `/dev/root'.
^C unfinished ...
-
/var/lib/dpkg/info/grub-pc.postinst is attached. I can't make sense of it.
BTW, I fixed the 'no space left on device' on the other machine with a btrfs
balance. No one seems to know this, but even though df reports that 64% of the
disk array is used, apparently one of the disks did get full somehow and was
preventing even a simple mkdir. But a balance fixed it.
I thought balancing was supposed to be automatic in BTRFS?
Is defrag not automatic?
On Thursday 5 May, 2011 12:55:44 you wrote:
Excerpts from CACook's message of 2011-05-05 15:50:02 -0400:
I was afraid of this finger-pointing.
We're not finger pointing, but we also don't maintain the script that is
failing. I'm happy to patch up bugs in the FS (or point you to newer
kernels that have them fixed) but at this point we don't have enough
info to say if it is an FS problem or a debian package problem.
Perhaps if you ran it under strace?
Other distros don't have problems with btrfs on /, so somehow this is
specific to debian's setup.
-chris
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
grub-pc.postinst
Description: application/shellscript
Re: Cannot Deinstall a Debian Package
On Thursday 5 May, 2011 13:31:17 cwillu wrote: I took the liberty of asking #debian, and they've requested that you file a bug in their bug tracker. They've also suggested that you might be able to short-circuit the faulty script in their kernel package via an exit 0, or even replace the faulty grub-probe by manually extracting the newer version of the package. I tried to install Debian's reportbug, but of course I can't. And assembling the info they need for email reporting will take me a half day of analysis. Part of the problem here is I am trying desperately to make a living in another line of business, and I don't have time for any of these problems. I don't know how to manually extract a package. I guess it's done with dpkg, but that will take more time for me to figure out. I've lost half of today already on this problem. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Thursday 5 May, 2011 13:40:25 cwillu wrote: Could you include the information I asked for previously? (Kernel version, output of btrfs fi df and btrfs fi show) Kernel 2.6.37-2 # btrfs fi df /home Data, RAID0: total=2.61TB, used=2.47TB Data: total=8.00MB, used=8.00MB System, RAID1: total=8.00MB, used=196.00KB System: total=4.00MB, used=0.00 Metadata, RAID1: total=6.88GB, used=4.64GB Metadata: total=8.00MB, used=0.00 # df /dev/sdb Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb 3907029168 2659716272 1242565920 69% /home # df /dev/sdc Filesystem 1K-blocks Used Available Use% Mounted on udev 1895384 268 1895116 1% /dev (this doesn't make any sense) # btrfs fi show failed to read /dev/sdg failed to read /dev/sdf failed to read /dev/sde failed to read /dev/sdd failed to read /dev/sr0 Label: none uuid: 85537aa8-30dc-4f87-ac55-6c8344304184 Total devices 2 FS bytes used 2.47TB devid1 size 1.82TB used 1.31TB path /dev/sdb devid2 size 1.82TB used 1.31TB path /dev/sdc Btrfs Btrfs v0.19 Defrag is not the same as balancing, and neither is quite the same as the balancing of the internal b-trees that make up the filesystem. I know they're not the same. But I am asking: I thought balancing was supposed to be automatic in BTRFS? Is defrag not automatic? No idea what 'balancing of the internal b-trees' is. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Thursday 5 May, 2011 13:59:23 Lars Wirzenius wrote: dpkg --fsys-tarfile foo.deb | tar -C / -tf - I was expecting this to extract into the local directory, although it seems to have extracted into the final destinations. Can't be sure. grub-setup -V gives the new version. change -t to -x to actually extract I don't see the distinction. It does seem to have extracted. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Thursday 5 May, 2011 14:48:49 cwillu wrote: How old was the filesystem? It might just have been lingering problems from an older kernel, which would be cleared up entirely by the balance you just ran. I specifically set up the filesystem with the Live CD of the M- release of Ubuntu, so as to be using a much newer kernel than Debian's. This was in December. Then I used the Debian net install CD in Expert mode to install the OS. I took all pains to be using the newest OS available to set up the disks, so as to take advantage of WD's Advanced Format, and the newest improvements to BTRFS. But the balance is still going after more than an hour. I am seeing drastically conflicting info from df and btrfs filesystem df, which is inexplicable. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Cannot Deinstall a Debian Package
Having a failure that may be because grub2 doesn't BTRFS. /boot is ext3 and / is BTRFS. # dpkg -r linux-image-2.6.32-5-amd64 (Reading database ... 136673 files and directories currently installed.) Removing linux-image-2.6.32-5-amd64 ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64 run-parts: executing /etc/kernel/postrm.d/zz-update-grub 2.6.32-5-amd64 /boot/vmlinuz-2.6.32-5-amd64 /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-2.6.32-5-amd64.postrm line 234. dpkg: error processing linux-image-2.6.32-5-amd64 (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.32-5-amd64 I can't install or remove packages, of do my dist-upgrades. What gives? -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
On Tuesday 3 May, 2011 14:26:52 Fajar A. Nugraha wrote: Does Debian (or whatever distro you use) support BTRFS /? If yes, you should ask them. What do you mean 'does Debian support BTRFS'? The kernel supports it. And why would they know more about BTRFS than you? My whole system is installed over BTRFS. If this is non-functional in any OS there should be a warning indicating it is non-functional. Looks like grub problem. I know that Ubuntu Natty's grub-pc (grub2) work just fine, so you might be able to fix it by upgrading to newer grub/grub-pc (perhaps from Debian-unstable). I would be happy to upgrade grub, but the package management system is jammed because of this. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Cannot Deinstall a Debian Package
I know what the error says; we've established that / is in fact mounted. The system boots and runs, but grub doesn't understand it. My only answer is that grub-probe does not understand BTRFS. The question is what to do about this. I have three major systems committed to this filesystem. Can you not see how this is an emergency? How is re-reading the error supposed to help anything? Or was your intention to help? On Tuesday 3 May, 2011 16:02:43 Chuck Burns wrote: On Tuesday, May 03, 2011 05:20:49 PM cac...@quantum-sci.com wrote: -snip- I would be happy to upgrade grub, but the package management system is jammed because of this. -snip- You should Re-read the error you posted. The package management system goes bonkers, because /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: How Snapshots Inter-relate?
On Thursday 21 April, 2011 11:47:25 Calvin Walton wrote: You have nothing to worry about. You can delete any snapshot on btrfs without losing data from any other snapshot. Each snapshot is completely independent. This works because data which is shared between multiple snapshots is reference counted, and won't be deleted until you remove the last snapshot that references that data. Wow. Awesome job, BTRFS team. Would it be good practice to say, once a year, do a completely new fresh snapshot? -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
How Snapshots Inter-relate?
I have set up a backup server in the garage which does rsync backups of all my servers weekly, and snapshots those backups. It works wonderfully, and I was able to set it up thanks to help from this listserv, thank you. But I'm accumulating quite a few backups now, unnecessarily. After a couple months I only need a representative one, once a month. I am afraid to delete three of my weekly snapshots out of each month, as I'm afraid they're cumulative. I might end up with nothing valid if each builds on the last, forever. How do I resolve this? -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Adding a disk fails
On Thu 20 January 2011 22:55:54 Hubert Kario wrote: You still have a btrfs on /dev/sdc, do a dd if=/dev/zero of=/dev/sdc bs=8192 (overkill, but I don't remember which blocks have to be zeroed to destroy btrfs superblock) I gave up and started over. Maybe it should be clarified in the wiki that no mkfs should be done on additional volumes, as it's counterintuitive to some. yes. rc.local is too late, unless you will also mount the volume from there and not using /etc/fstab How and when then? That depends - it has to be done before mounting. And if the device is part of the boot partition then you may put the scan command into an init-ramdisk. This does not seem to have been sent to the listserv, as I only got it in a reply. This is likely incomplete. Using something like device=/dev/sdb,device=/dev/sdc on fstab mount options should also work. You mean as a substitute for a scan? On my other server the btrfs array seems to mount just fine without any measures to scan. I don't understand this, nor why no specific advice is given about scanning on boot in the wiki. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Backup Command
Well thanks to some help from you guys I seem to have my backup server almost fully running and functional with rsync. Amazing functions, this snapshotting and rsync. I still don't know why I cannot remove snapshots though. (Debian Testing with 2.6.32-28) And I don't know how to reach out from the backup server to the HTPC and stop MythTV there, so I can export the Mysql database safely, from a cron job on the backup server. Suggestions? -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Adding a disk fails
On Fri 21 January 2011 10:42:39 Goffredo Baroncelli wrote: Thanks Goffredo but as I say, I did this and it responds with ERROR: error adding the device '/dev/sdc' .. it doesn't give a clue. In your email you wrote that before adding the device you format it. Anyway I don't think that this is the problem. Have you check which is reported in dmesg. Absolutely no sign of a problem in dmesg or the logs. btrfs device scan This must be done at every boot? If so, where is recommended, in rc.local? Look at this thread, where I wrote anout a possible solution http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg04709.html Thanks. I am suspecting scan is built into Debian. Not sure what to look for though, with all the darned variables. 2.6.32-5-amd64 with Debian patches. From a btrfs point of view, it is a very old kernel. IIRC in this kernel is not supported the snapshot removal. I suggest you to update the kernel with a recent one. I've looked for a newer kernel sources, but there isn't one with Debian patches. I always compile my kernel. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Backup Command
On Fri 21 January 2011 11:44:24 Freddie Cash wrote: #!/bin/sh ssh someu...@mythtv.pc /path/to/some/script stop /path/to/your/rsync/script ssh someu...@mythtv.pc /path/to/some/script start Ho-lee crap, this is fantastic. Everything seems to work. I find though that if I stop myth -and- mysql, I cannot export the database, so I only stop Myth. It's the only thing using the database anyway, in my case. Well it's been 12 hours and I'm still doing my first HTPC data transfer, so not all commands are tested (untested==#), but I am confident they will work. I'm donating my (weekly) cron script here in case it helps someone. (below) I have four systems: hex - work laptop droog - HTPC with a 4TB btrfs raid0 array on /home and 500GB raptor on / slepnir - backup server in a cube case out in the garage (in case of theft or fire) with a SuperMicro 5 disk hot-swap cage, 6TB so far. (WD Green 2TB now $80 with rebate!) phone - Android Nexus One with 16GB SD The backup server has SSH credentials on the other systems, but only the work laptop can ssh to it (limited by Shorewall). The backup server will also handle security cameras and will presumably dnat a port to the HTPC, which will serve it to the WAN on SSH (reverse tunnel) so I can get motion notifications and video on my phone. (ZoneMinder) The HTPC is the only system allowed to present anything to the WAN as it has nothing sensitive, and -that- will be on a subnet. Maybe I can limit it to my phone's IP. I do have a (disused) WindowsXP partition, but unsure how to back that up. Maybe ssh with a dd command. Thanks for the help all. backups - #!/bin/sh # # cron.weekly/backups -- schedules periodic backups of darkmatter systems # # Copyleft © Carl Cook # #--archive is equivalent to 'recursive links perms times group owner DevicesSpecials' /bin/mount /media/backups #-- # Hex #/sbin/btrfs subvolume snapshot /media/backups/hex-home/ /media/backups/hex-home-snap-$(date +%Y-%m-%d) /usr/bin/rsync --archive --checksum --compress --hard-links --delete-during --delete-excluded --inplace --numeric-ids --log-file=/media/backups/hex-home-$(date +%Y-%m-%d).log -e ssh root@hex:///home/ /media/backups/hex-home/ #/sbin/btrfs subvolume snapshot /media/backups/hex-root/ /media/backups/hex-root-snap-$(date +%Y-%m-%d) #/usr/bin/rsync --archive --checksum --compress --hard-links --delete-during --delete-excluded --inplace --numeric-ids --exclude-from=/media/backups/exclude-root --log-file=/media/backups/hex-root-$(date +%Y-%m-%d).log -e ssh root@hex:/// /media/backups/hex-root/ #-- # Droog #/sbin/btrfs subvolume snapshot /media/backups/droog-home/ /media/backups/droog-home-snap-$(date +%Y-%m-%d) /usr/bin/rsync --archive --checksum --compress --hard-links --delete-during --delete-excluded --inplace --numeric-ids --log-file=/media/backups/droog-home-$(date +%Y-%m-%d).log -e ssh root@droog:///home/ /media/backups/droog-home/ /usr/bin/ssh root@droog /etc/init.d/mythtv-backend stop /usr/bin/ssh root@droog /usr/bin/mysqldump -u mythtv -pmythtv mythconverg -c /home/bill/.mythtv/mysql_backup-$(date +%Y-%m-%d).sql /usr/bin/ssh root@droog /etc/init.d/mythtv-backend start /sbin/btrfs subvolume snapshot /media/backups/droog-root/ /media/backups/droog-root-snap-$(date +%Y-%m-%d) /usr/bin/rsync --archive --checksum --compress --hard-links --delete-during --delete-excluded --inplace --numeric-ids --exclude-from=/media/backups/exclude-root --log-file=/media/backups/droog-root-$(date +%Y-%m-%d).log -e ssh root@droog:/// /media/backups/droog-root/ #-- # Phone #/sbin/btrfs subvolume snapshot /media/backups/phone-sd/ /media/backups/phone-sd-snap-$(date +%Y-%m-%d) #/usr/bin/rsync --archive --checksum --compress --hard-links --delete-during --delete-excluded --inplace --numeric-ids --log-file=/media/backups/phone-sd-$(date +%Y-%m-%d).log -e ssh root@hex:///media/disk-1/ /media/backups/phone-sd/ #-- /bin/umount /media/backups - -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
