From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: ubirmvol:ing gluebied volumes
Date: Fri, 06 May 2011 22:07:45 +0300 [thread overview]
Message-ID: <1304708865.7222.106.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.1105061412050.15966@lnxricardw.se.axis.com>
On Fri, 2011-05-06 at 14:17 +0200, Ricard Wanderlof wrote:
> I enabled the gluebi MTD emulation layer in the kernel, and was pleased to
> see all the UBI volumes coming up in /proc/mtd as mtd volumes.
Hehe :-)
> However, one thing though, if I try to ubirmvol one of the UBI volumes, I
> get:
>
> ubirmvol: error!: cannot UBI remove volume
> error 16 (Device or resource busy)
Yeah.
> similar to what I get if I have a mounted ubifs residing in an UBI volume
> and try and ubirmvol the volume without umounting the file system.
Yes.
> Fair enough, I guess gluebi is keeping the UBI volume busy? But then how
> do I free it up?
I think the only way is to rmmod gluebi.
> There's normally no way to disassociate mtd partitions
> from the underlying media, and I can't see any ubi tool that would do this
> either.
Right.
> So is this an (unfortunate) consequence of using gluebi: that the
> underlying UBI volumes can't be removed?
In current implementation yes. But you can rmomod it, shuffle UBI
volumes, and modprobe it again.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-05-06 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 12:17 ubirmvol:ing gluebied volumes Ricard Wanderlof
2011-05-06 19:07 ` Artem Bityutskiy [this message]
2011-05-09 6:49 ` Ricard Wanderlof
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1304708865.7222.106.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox