Re: btrfs: could not do orphan cleanup -22
Reartes Guillermo wrote (ao): [ 71.617841] device label testfs1 devid 1 transid 4143 /dev/sdb1 [ 71.619164] btrfs: disk space caching is enabled [ 71.629969] device label fedora devid 1 transid 2038 /dev/sda2 [ 71.805339] btrfs: Error removing orphan entry, stopping orphan cleanup [ 71.806597] btrfs: could not do orphan cleanup -22 [ 71.986601] device label testfs1 devid 1 transid 4143 /dev/sdb1 [ 72.934724] btrfs: open_ctree failed Since sda2 is mounted i could not check it, but from the logs it is not clear to me if the issue is in sda2 or sdb1. Seems sda2 from the above. -- 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
[Lsf-pc] [CFP] Linux Storage, Filesystem and Memory Management Summit 2013
The annual Linux Storage, Filesystem and Memory Management Summit for 2013 will be held on April 18th and 19th following the Linux Foundation Collaboration Summit at Parc 55 Hotel in San Francisco, CA: https://events.linuxfoundation.org/events/collaboration-summit https://events.linuxfoundation.org/events/lsfmm-summit We'd therefore like to issue a call for agenda proposals that are suitable for cross-track discussion as well as more technical subjects for discussion in the breakout sessions. 1) Suggestions for agenda topics should be sent before February 8th 2013 to: lsf...@lists.linux-foundation.org and optionally cc the Linux list which would be most interested in it: ATA: linux-...@vger.kernel.org SCSI: linux-s...@vger.kernel.org FS: linux-fsde...@vger.kernel.org MM: linux...@kvack.org Please remember to tag your subject with [LSF/MM TOPIC] to make it easier to track. Agenda topics and attendees will be selected by the program committee, but the final agenda will be formed by consensus of the attendees on the day. We'll try to cap attendance at around 25-30 per track to facilitate discussions although the final numbers will depend on the room sizes at the venue. 2) Requests to attend the summit should be sent to: lsf...@lists.linux-foundation.org Please summarize what expertise you will bring to the meeting, and what you'd like to discuss. please also tag your email with [ATTEND] so there's less chance of it getting lost in the large mail pile. Presentations are allowed to guide discussion, but are strongly discouraged. There will be no recording or audio bridge. However, written minutes will be published as in previous years: 2012: http://lwn.net/Articles/490114/ http://lwn.net/Articles/490501/ 2011: http://lwn.net/Articles/436871/ http://lwn.net/Articles/437066/ 2010: http://lwn.net/Articles/399148/ http://lwn.net/Articles/399313/ http://lwn.net/Articles/400589/ 2009: http://lwn.net/Articles/327601/ http://lwn.net/Articles/327740/ http://lwn.net/Articles/328347/ Prior years: http://www.usenix.org/events/lsf08/tech/lsf08sums.pdf http://www.usenix.org/publications/login/2007-06/openpdfs... 3) If you have feedback on last year's meeting that we can use to improve this year's, please also send that to: lsf...@lists.linux-foundation.org Thank you on behalf of the program committee: Storage: Martin K. Petersen Jens Axboe James Bottomley Filesystems: Ric Wheeler Christoph Hellwig Jaegeuk Kim Jeffrey Layton Tao Ma Chris Mason Trond Myklebust Eric Sandeen Theodore Ts'o Sage Weil MM: Rik van Riel Mel Gorman Ying Han ___ Lsf-pc mailing list lsf...@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/lsf-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: btrfs: could not do orphan cleanup -22
On Thu, Jan 17, 2013 at 05:23:17PM -0300, Reartes Guillermo wrote: [7.008342] device label testfs1 devid 1 transid 4141 /dev/sdb1 [7.011071] btrfs: disk space caching is enabled [7.165692] btrfs: Error removing orphan entry, stopping orphan cleanup [7.165696] btrfs: could not do orphan cleanup -22 [8.910980] btrfs: open_ctree failed The orphan cleaning messages are harmless (and not useful to users anyway), not like the failed mount. As a workaround, mount it read-only and remount read write. It should be fixed after first mount cycle. We've seen the -22 error during testing and Josef is aware of that, so it's going to be fixed after the checksum problems. [8.944598] systemd-journald[292]: Received SIGTERM [ 70.616949] systemd-modules-load[453]: Module 'uinput' is already loaded [ 70.676072] systemd-udevd[457]: starting version 197 [ 70.937319] microcode: AMD CPU family 0x6 not supported [ 71.598671] btrfs: disk space caching is enabled [ 71.617841] device label testfs1 devid 1 transid 4143 /dev/sdb1 [ 71.619164] btrfs: disk space caching is enabled [ 71.629969] device label fedora devid 1 transid 2038 /dev/sda2 [ 71.805339] btrfs: Error removing orphan entry, stopping orphan cleanup [ 71.806597] btrfs: could not do orphan cleanup -22 [ 71.986601] device label testfs1 devid 1 transid 4143 /dev/sdb1 [ 72.934724] btrfs: open_ctree failed I booted first with 3.8.0-0.rc3.git1.1.fc19 (which has a lot of issues) and then back with 3.7.2-201.fc18. I don't see from the messages under which kernel it happened, but I assume with both. david -- 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: [PATCH V5] Btrfs: snapshot-aware defrag
On Thu, Jan 17, 2013 at 08:42:46AM -0600, Mitch Harder wrote: [16028.160002] RAX: dead00200200 RBX: 8800 RCX: 00018e20 [16028.160002] RDX: dead00100100 RSI: 001b RDI: 001b RAX: dead00200200 RDX: dead00100100 list_head poisons to mark deleted entries I've tried to trap the error with a BUG_ON prior to deleting the list, but my attempt isn't catching the error: @@ -1769,6 +1769,7 @@ int btrfs_clean_old_snapshots(struct btrfs_root *root) int ret; root = list_entry(list.next, struct btrfs_root, root_list); + BUG_ON(root-root_list == NULL); You're taking an address and comparing it to NULL? This works, but in under very limited conditions :) If root is not null, then the structure is valid, but the root_list hook is not valid anymore, ie. an inconsistency. david -- 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: [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1
On 01/17/2013 12:47 PM, David Sterba wrote: Hi Chris, please pull a few more fixes to the 0.20-rc series. I have reviewed and verified them where possible. There are the long awaited ARM fixes, help updates and unsorted code fixes. git://repo.or.cz/btrfs-progs-unstable/devel.git for-chris Based on top of master commit 91d9eec1ff044394f2b98ee7fcb76713dd33b994 Thanks. david --- btrfs-list.c | 69 +- btrfsck.c |3 +- cmds-filesystem.c | 26 cmds-inspect.c|5 ++- cmds-receive.c|4 ++- cmds-scrub.c |4 ++- cmds-send.c |9 ++- convert.c |5 +++ ctree.h |8 -- debug-tree.c | 10 +++ disk-io.c | 13 -- kerncompat.h | 12 + man/btrfs.8.in|4 --- mkfs.c| 35 ++- restore.c |7 +++-- utils.c | 48 + utils.h |2 + version.sh|2 - volumes.c |8 +++--- 19 files changed, 159 insertions(+), 115 deletions(-) --- Alex Lyakas (1): btrfs-progs: Receive: preserve ownership for symlinks, by using 'lchown' Arne Jansen (1): Btrfs-progs: fix unaligned accesses David Sterba (2): btrfs-progs: do not send stream into a terminal btrfs-progs: ignore -a option in mkfs Goffredo Baroncelli (3): Move parse_size() to utils.[hc] parse_size(): replace atoll() with strtoull() parse_size(): add new suffixes Kenji Okimoto (3): btrfs-progs: plug a memory leak reported by cppcheck btrfs-progs: check malloc() result btrfs-progs: plug memory leaks in btrfs_scan_one_dir() reported by cppcheck. Lluis Batlle i Rossell (1): btrfs-progs: Fix getopt on arm platforms Sergei Trofimovich (1): version.sh: fix version when built from tarball While you are about it, how about adding in this fix from Dieter Ries to fix version a little more: http://article.gmane.org/gmane.comp.file-systems.btrfs/20069 Simon Xu (2): btrfs-progs: remove device show from btrfs man page btrfs-progs: remove '-h' from btrfs man page Wade Cline (1): Btrfs-progs: Fix compiler warnings on PPC64 Wang Sheng-Hui (3): btrfs-progs: add -V description in print_usage btrfs-progs: update usage description for debug-tree.c btrfs-progs: print the right mount checking info in restore.c Zach Brown (1): btrfs-progs: fix 32bit int/pointer cast warnings -- 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
unresolved ref dir
Hi everyone, Few days ago, during a system update, some errors appeard: can't create file XXX (Input/Output errors). ls, stat, rm, on these files gave always the same Input/output error. btrfsck --repair told me that some leaves were corrupt (bad key order) but nothing changed. They were all in the same folder so i tried to move its contents into another dir and delete it. Surprisingly it fixed some bad files but i got new errors. Trying to delete the file kgthemeselector.h gives these kernel messages: [ 814.056583] device label system devid 1 transid 32432 /dev/sda4 [ 814.058370] btrfs: use ssd allocation scheme [ 814.058394] btrfs: use lzo compression [ 814.058403] btrfs: enabling auto defrag [ 814.058413] btrfs: enabling auto recovery [ 814.058418] btrfs: disk space caching is enabled [ 814.060856] btrfs: mismatching generation and generation_v2 found in root item. This root was probably mounted with an older kernel. Resetting all new fields. [ 834.384784] btrfs: unlinked 1 orphans [ 846.062494] btrfs failed to delete reference to kgthemeselector.h, inode 538801 parent 419 [ 846.062506] [ cut here ] [ 846.062579] WARNING: at fs/btrfs/super.c:246 __btrfs_abort_transaction+0x99/0xb0 [btrfs]() [ 846.062585] Hardware name: System Product Name [ 846.062590] btrfs: Transaction aborted [ 846.062595] Modules linked in: [ 846.062600] fuse btusb ext4 jbd2 mbcache arc4 powernow_k8 ath9k mperf ath9k_common ath9k_hw kvm_amd eeepc_wmi asus_wmi ath3k ath kvm sparse_keymap video mac80211 bluetooth pci_hotplug crc16 cfg80211 snd_hda_codec_realtek rfkill radeon microcode snd_hda_codec_hdmi r8169 psmouse ttm drm_kms_helper k10temp serio_raw snd_hda_intel pcspkr sp5100_tco drm mii snd_hda_codec agpgart joydev evdev snd_hwdep i2c_piix4 i2c_algo_bit snd_pcm snd_page_alloc snd_timer i2c_core snd wmi soundcore button processor sha256_generic ablk_helper cryptd aes_i586 aes_generic cbc hid_generic usbhid hid usb_storage dm_crypt dm_mod btrfs crc32c libcrc32c zlib_deflate sd_mod ata_generic pata_acpi ohci_hcd ahci libahci xhci_hcd pata_atiixp libata ehci_hcd scsi_mod usbcore usb_common [ 846.062747] Pid: 1730, comm: rm Not tainted 3.6.11-1-ARCH #1 [ 846.062753] Call Trace: [ 846.062774] [c1039fc2] warn_slowpath_common+0x72/0xa0 [ 846.062814] [f8a33da9] ? __btrfs_abort_transaction+0x99/0xb0 [btrfs] [ 846.062965] [f8a33da9] ? __btrfs_abort_transaction+0x99/0xb0 [btrfs] [ 846.062977] [c103a093] warn_slowpath_fmt+0x33/0x40 [ 846.063031] [f8a33da9] __btrfs_abort_transaction+0x99/0xb0 [btrfs] [ 846.063086] [f8a63247] __btrfs_unlink_inode+0x357/0x360 [btrfs] [ 846.063135] [f8a66323] btrfs_unlink_inode+0x33/0x60 [btrfs] [ 846.063180] [f8a663b8] btrfs_unlink+0x68/0xc0 [btrfs] [ 846.063192] [c11472b1] vfs_unlink+0x81/0xf0 [ 846.063201] [c1147445] do_unlinkat+0x125/0x140 [ 846.063214] [c104281c] ? irq_exit+0x5c/0xa0 [ 846.063228] [c1149292] sys_unlinkat+0x22/0x50 [ 846.063239] [c13e06df] sysenter_do_call+0x12/0x28 [ 846.063246] ---[ end trace 158e903eaeb56eb1 ]--- [ 846.063255] BTRFS error (device sda4) in __btrfs_unlink_inode:2810: error 2 [ 846.063262] btrfs is forced readonly And btrfs --repair gives checking extents checking fs roots root 256 inode 266753 errors 2000 unresolved ref dir 419 index 2091 namelen 17 name kgthemeselector.h filetype 1 error 1 root 256 inode 538801 errors 2000 unresolved ref dir 419 index 0 namelen 17 name kgthemeselector.h filetype 1 error 6 enabling repair mode found 18558943232 bytes used err is 0 total csum bytes: 17455544 total tree bytes: 434208768 total fs tree bytes: 386076672 btree space waste bytes: 102939178 file data blocks allocated: 26994438144 referenced 21001273344 Btrfs Btrfs v0.19 I'm on a 64 bit Arch Linux up to date, uname gives Linux ... 3.6.11-1-ARCH #1 SMP PREEMPT ... x86_64 GNU/Linux Is there a way to get rid of these files? Thanks! -- Christophe Calvès -- 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: [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1
On Fri, Jan 18, 2013 at 09:16:00AM -0500, Gene Czarcinski wrote: Sergei Trofimovich (1): version.sh: fix version when built from tarball While you are about it, how about adding in this fix from Dieter Ries to fix version a little more: http://article.gmane.org/gmane.comp.file-systems.btrfs/20069 I did not notice it before, but Dieter's patch does not work when progs are built from .git repository -echo #define BTRFS_BUILD_VERSION \Btrfs $v\ .build-version.h +echo #define BTRFS_BUILD_VERSION \$v\ .build-version.h $v is set with the git tag, so the Btrfs string does not appear in the output (eg. mkfs.btrfs). Technically, $v should always contain some sort of a tag, Sergei's patch hardcodes it to the latest one for the non-git case. This is IMHO the right approach. david -- 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: [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1
On 01/17/2013 12:47 PM, David Sterba wrote: Hi Chris, please pull a few more fixes to the 0.20-rc series. I have reviewed and verified them where possible. There are the long awaited ARM fixes, help updates and unsorted code fixes. git://repo.or.cz/btrfs-progs-unstable/devel.git for-chris Based on top of master commit 91d9eec1ff044394f2b98ee7fcb76713dd33b994 Thanks. david --- btrfs-list.c | 69 +- btrfsck.c |3 +- cmds-filesystem.c | 26 cmds-inspect.c|5 ++- cmds-receive.c|4 ++- cmds-scrub.c |4 ++- cmds-send.c |9 ++- convert.c |5 +++ ctree.h |8 -- debug-tree.c | 10 +++ disk-io.c | 13 -- kerncompat.h | 12 + man/btrfs.8.in|4 --- mkfs.c| 35 ++- restore.c |7 +++-- utils.c | 48 + utils.h |2 + version.sh|2 - volumes.c |8 +++--- 19 files changed, 159 insertions(+), 115 deletions(-) --- Alex Lyakas (1): btrfs-progs: Receive: preserve ownership for symlinks, by using 'lchown' Arne Jansen (1): Btrfs-progs: fix unaligned accesses David Sterba (2): btrfs-progs: do not send stream into a terminal btrfs-progs: ignore -a option in mkfs Goffredo Baroncelli (3): Move parse_size() to utils.[hc] parse_size(): replace atoll() with strtoull() parse_size(): add new suffixes Kenji Okimoto (3): btrfs-progs: plug a memory leak reported by cppcheck btrfs-progs: check malloc() result btrfs-progs: plug memory leaks in btrfs_scan_one_dir() reported by cppcheck. Lluis Batlle i Rossell (1): btrfs-progs: Fix getopt on arm platforms Sergei Trofimovich (1): version.sh: fix version when built from tarball Simon Xu (2): btrfs-progs: remove device show from btrfs man page btrfs-progs: remove '-h' from btrfs man page Wade Cline (1): Btrfs-progs: Fix compiler warnings on PPC64 Wang Sheng-Hui (3): btrfs-progs: add -V description in print_usage btrfs-progs: update usage description for debug-tree.c btrfs-progs: print the right mount checking info in restore.c Zach Brown (1): btrfs-progs: fix 32bit int/pointer cast warnings David, first of all let me thank you for pulling these together. I do not believe I am alone in wondering what was happening to the btrfs-progs patches on the mailing list. I would like to recommend some additional patches for inclusion since they are currently part of the Fedora 18 btrfs-tools package. Josef Bacik: detect if the disk we are formatting is a ssd V2 http://article.gmane.org/gmane.comp.file-systems.btrfs/18749 This one may be a little more of a problem since the suggested man update is missing and there is a second part for the kernel (status unknown). Josef Bacik: add btrfs device ready command http://article.gmane.org/gmane.comp.file-systems.btrfs/18129 Since Fedora uses a stock a kernel as possible, I suspect the corresponding patch is applied. There are two or three other patches that appear to make sense but I have no idea if they have been submitted. Gene -- 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: [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1
On 01/18/2013 09:44 AM, David Sterba wrote: On Fri, Jan 18, 2013 at 09:16:00AM -0500, Gene Czarcinski wrote: Sergei Trofimovich (1): version.sh: fix version when built from tarball While you are about it, how about adding in this fix from Dieter Ries to fix version a little more: http://article.gmane.org/gmane.comp.file-systems.btrfs/20069 I did not notice it before, but Dieter's patch does not work when progs are built from .git repository -echo #define BTRFS_BUILD_VERSION \Btrfs $v\ .build-version.h +echo #define BTRFS_BUILD_VERSION \$v\ .build-version.h $v is set with the git tag, so the Btrfs string does not appear in the output (eg. mkfs.btrfs). Technically, $v should always contain some sort of a tag, Sergei's patch hardcodes it to the latest one for the non-git case. This is IMHO the right approach. OK, I see what you mean. However, the current situation when btrfs is built from a tarball results in: btrfs --version Btrfs Btrfs v0.19 and mkfs.btrfs -V mkfs.btrfs, part of Btrfs Btrfs v0.19 There must be a way to reliably just have one Btrfs and I will look into it. Gene -- 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: [GIT PULL] btrfs-progs: more bugfixes for 0.20-rc1
On Fri, Jan 18, 2013 at 10:49:20AM -0500, Gene Czarcinski wrote: On 01/18/2013 09:44 AM, David Sterba wrote: On Fri, Jan 18, 2013 at 09:16:00AM -0500, Gene Czarcinski wrote: Sergei Trofimovich (1): version.sh: fix version when built from tarball While you are about it, how about adding in this fix from Dieter Ries to fix version a little more: http://article.gmane.org/gmane.comp.file-systems.btrfs/20069 I did not notice it before, but Dieter's patch does not work when progs are built from .git repository -echo #define BTRFS_BUILD_VERSION \Btrfs $v\ .build-version.h +echo #define BTRFS_BUILD_VERSION \$v\ .build-version.h $v is set with the git tag, so the Btrfs string does not appear in the output (eg. mkfs.btrfs). Technically, $v should always contain some sort of a tag, Sergei's patch hardcodes it to the latest one for the non-git case. This is IMHO the right approach. OK, I see what you mean. However, the current situation when btrfs is built from a tarball results in: btrfs --version Btrfs Btrfs v0.19 I guess one problem here is that there's no canonical way of generating a tarball (without the git files) from a git checkout, with detailed version information. So what's happening, I suspect, is that the distributions/people producing source tarballs of btrfs-progs are checking out the git tree, deleting .git, and tarring up that, which loses any git versioning. I think a solution may be to have a dist or tar make target which does the above automatically and includes a suitably-generated version.h in the tarball. Hugo. and mkfs.btrfs -V mkfs.btrfs, part of Btrfs Btrfs v0.19 There must be a way to reliably just have one Btrfs and I will look into it. Gene -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Klytus, I'm bored. What plaything can you offer me today? --- signature.asc Description: Digital signature
