headers
Olivier Bonvalet | 15 Aug 2012 19:28
Picon

Can't umount a read-only FS ?

Hi,

I have a strange problem with a btrfs partition : after an error, btrfs was forced readonly.

So I try to umount it, to launch btrfsck, but it doesn't work :

root! sofia:~# umount /backup/
root! sofia:~# btrfsck /dev/vg-sofia/backup
/dev/vg-sofia/backup is currently mounted. Aborting.
root! sofia:~# umount /backup/
umount: /backup/: not mounted
root! sofia:~# btrfsck /dev/vg-sofia/backup
/dev/vg-sofia/backup is currently mounted. Aborting.
root! sofia:~#

And I can't remount it :

root! sofia:~# mount /backup/
mount: /dev/mapper/vg--sofia-backup already mounted or /backup busy

Or access to the content :

root! sofia:~# ls /backup/
root! sofia:~#

It's on a v3.4.7 kernel, with btrfs-tools version 0.19+20120328-7 (from Debian unstable).

What should I do ? Reboot ?

Thanks,
(Continue reading)

Permalink | Reply |
headers
Olivier Bonvalet | 15 Aug 2012 19:32
Picon

Re: Can't umount a read-only FS ?

On 15/08/2012 19:28, Olivier Bonvalet wrote:
> Hi,
> 
> I have a strange problem with a btrfs partition : after an error, btrfs was forced readonly.
> 
> So I try to umount it, to launch btrfsck, but it doesn't work :
> 

I forgot, it was set readonly after that error :

Aug 15 09:44:33 sofia kernel: [29840.510826] ------------[ cut here ]------------
Aug 15 09:44:33 sofia kernel: [29840.510850] WARNING: at fs/btrfs/super.c:219
__btrfs_abort_transaction+0x3a/0x95 [btrfs]()
Aug 15 09:44:33 sofia kernel: [29840.510858] btrfs: Transaction aborted
Aug 15 09:44:33 sofia kernel: [29840.510860] Modules linked in: ipv6 btrfs zram(C) nf_conntrack
Aug 15 09:44:33 sofia kernel: [29840.510872] Pid: 26524, comm: btrfs Tainted: G         C   2.6.44.7-dae-xen #2
Aug 15 09:44:33 sofia kernel: [29840.510879] Call Trace:
Aug 15 09:44:33 sofia kernel: [29840.510893]  [<ffffffff8103c7cf>] ? warn_slowpath_common+0x76/0x8a
Aug 15 09:44:33 sofia kernel: [29840.510901]  [<ffffffff8103c87b>] ? warn_slowpath_fmt+0x45/0x4a
Aug 15 09:44:33 sofia kernel: [29840.510924]  [<ffffffffa0077346>] ?
btrfs_alloc_delayed_item+0x13/0x3b [btrfs]
Aug 15 09:44:33 sofia kernel: [29840.510941]  [<ffffffffa00203d2>] ?
__btrfs_abort_transaction+0x3a/0x95 [btrfs]
Aug 15 09:44:33 sofia kernel: [29840.510964]  [<ffffffffa0042c80>] ?
btrfs_unlink_subvol+0x1cf/0x255 [btrfs]
Aug 15 09:44:33 sofia kernel: [29840.510987]  [<ffffffffa0062178>] ?
btrfs_ioctl_snap_destroy+0x2e0/0x42c [btrfs]
Aug 15 09:44:33 sofia kernel: [29840.511010]  [<ffffffffa0064f8c>] ? btrfs_ioctl+0x4f6/0xfce [btrfs]
Aug 15 09:44:33 sofia kernel: [29840.511022]  [<ffffffff81021ffa>] ? do_page_fault+0x274/0x2f2
Aug 15 09:44:33 sofia kernel: [29840.511031]  [<ffffffff810d39ca>] ? vfs_ioctl+0x1e/0x31
(Continue reading)

Permalink | Reply |
headers
David Sterba | 15 Aug 2012 19:43
Picon

Re: Can't umount a read-only FS ?

Hi,

On Wed, Aug 15, 2012 at 07:32:45PM +0200, Olivier Bonvalet wrote:
> On 15/08/2012 19:28, Olivier Bonvalet wrote:
> > I have a strange problem with a btrfs partition : after an error, btrfs was forced readonly.
> 
> I forgot, it was set readonly after that error :
> 
> Aug 15 09:44:33 sofia kernel: [29840.510826] ------------[ cut here ]------------
> Aug 15 09:44:33 sofia kernel: [29840.510850] WARNING: at fs/btrfs/super.c:219
__btrfs_abort_transaction+0x3a/0x95 [btrfs]()
> Aug 15 09:44:33 sofia kernel: [29840.510858] btrfs: Transaction aborted
> Aug 15 09:44:33 sofia kernel: [29840.510860] Modules linked in: ipv6 btrfs zram(C) nf_conntrack
> Aug 15 09:44:33 sofia kernel: [29840.510872] Pid: 26524, comm: btrfs Tainted: G         C   2.6.44.7-dae-xen #2
> Aug 15 09:44:33 sofia kernel: [29840.510879] Call Trace:
> Aug 15 09:44:33 sofia kernel: [29840.510893]  [<ffffffff8103c7cf>] ? warn_slowpath_common+0x76/0x8a
> Aug 15 09:44:33 sofia kernel: [29840.510901]  [<ffffffff8103c87b>] ? warn_slowpath_fmt+0x45/0x4a
> Aug 15 09:44:33 sofia kernel: [29840.510924]  [<ffffffffa0077346>] ?
btrfs_alloc_delayed_item+0x13/0x3b [btrfs]
> Aug 15 09:44:33 sofia kernel: [29840.510941]  [<ffffffffa00203d2>] ?
__btrfs_abort_transaction+0x3a/0x95 [btrfs]
> Aug 15 09:44:33 sofia kernel: [29840.510964]  [<ffffffffa0042c80>] ?
btrfs_unlink_subvol+0x1cf/0x255 [btrfs]

my stack pattern recognition leads to this patch:

http://article.gmane.org/gmane.comp.file-systems.btrfs/19105
[PATCH] Btrfs: fix enospc problems when deleting a subvol

part of 3.6-rc and will probably end up in a stable updates of some 3.x.y
(Continue reading)

Permalink | Reply |
headers
Olivier Bonvalet | 15 Aug 2012 22:23
Picon

Re: Can't umount a read-only FS ?

Ok, thanks. So I will wait for the 3.5.3 kernel (since 3.5.2 don't seem to have any btrfs fix).

On 15/08/2012 19:43, David Sterba wrote:
> Hi,
> 
> On Wed, Aug 15, 2012 at 07:32:45PM +0200, Olivier Bonvalet wrote:
>> On 15/08/2012 19:28, Olivier Bonvalet wrote:
>>> I have a strange problem with a btrfs partition : after an error, btrfs was forced readonly.
>>
>> I forgot, it was set readonly after that error :
>>
>> Aug 15 09:44:33 sofia kernel: [29840.510826] ------------[ cut here ]------------
>> Aug 15 09:44:33 sofia kernel: [29840.510850] WARNING: at fs/btrfs/super.c:219
__btrfs_abort_transaction+0x3a/0x95 [btrfs]()
>> Aug 15 09:44:33 sofia kernel: [29840.510858] btrfs: Transaction aborted
>> Aug 15 09:44:33 sofia kernel: [29840.510860] Modules linked in: ipv6 btrfs zram(C) nf_conntrack
>> Aug 15 09:44:33 sofia kernel: [29840.510872] Pid: 26524, comm: btrfs Tainted: G         C   2.6.44.7-dae-xen #2
>> Aug 15 09:44:33 sofia kernel: [29840.510879] Call Trace:
>> Aug 15 09:44:33 sofia kernel: [29840.510893]  [<ffffffff8103c7cf>] ? warn_slowpath_common+0x76/0x8a
>> Aug 15 09:44:33 sofia kernel: [29840.510901]  [<ffffffff8103c87b>] ? warn_slowpath_fmt+0x45/0x4a
>> Aug 15 09:44:33 sofia kernel: [29840.510924]  [<ffffffffa0077346>] ?
btrfs_alloc_delayed_item+0x13/0x3b [btrfs]
>> Aug 15 09:44:33 sofia kernel: [29840.510941]  [<ffffffffa00203d2>] ?
__btrfs_abort_transaction+0x3a/0x95 [btrfs]
>> Aug 15 09:44:33 sofia kernel: [29840.510964]  [<ffffffffa0042c80>] ?
btrfs_unlink_subvol+0x1cf/0x255 [btrfs]
> 
> my stack pattern recognition leads to this patch:
> 
> http://article.gmane.org/gmane.comp.file-systems.btrfs/19105
(Continue reading)

Permalink | Reply |
headers
Olivier Bonvalet | 16 Aug 2012 00:29
Picon

[solved] Re: Can't umount a read-only FS ?

On 15/08/2012 19:28, Olivier Bonvalet wrote:
> Hi,
> 
> I have a strange problem with a btrfs partition : after an error, btrfs was forced readonly.
> 
> So I try to umount it, to launch btrfsck, but it doesn't work :
> 
> root! sofia:~# umount /backup/
> root! sofia:~# btrfsck /dev/vg-sofia/backup
> /dev/vg-sofia/backup is currently mounted. Aborting.
> root! sofia:~# umount /backup/
> umount: /backup/: not mounted
> root! sofia:~# btrfsck /dev/vg-sofia/backup
> /dev/vg-sofia/backup is currently mounted. Aborting.
> root! sofia:~#
> 
> 

Well... I was using a "mount --bind" of a directory within that FS... So not btrfs related.

Sorry for noise, once again.

Olivier

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
(Continue reading)

Permalink | Reply |

Gmane