[Unionfs] Umounting initrd image
Ram Kumar
ramkumar512 at gmail.com
Fri Mar 17 04:29:56 EST 2006
Hi,
If I try to umount my initrd image I get the following message.
umount: /oldroot: Device or resource busy
In my case I create the union by mounting two /dev/hda* (rw and ro)
partitions on the directories created in RamDisk and pivot_root into the new
union. So I think this error message is natural as these are already
mounted. But is there a better way to create the union from initrd image and
umount when not required ? Iam using 2.4.25 kernel
On 3/17/06, Tomas M <tomas at linux-live.org> wrote:
>
> If you use pivot_root, old root is moved to a directory you specified.
> So just unmount it and then use the following command to free initrd
> from RAM:
>
> /sbin/blockdev --flushbufs /dev/rd/0
>
> The blockdev command can be used only _after_ init starts so you'll need
> to add it to your startup scripts, you can't execute it from linuxrc.
>
> I'm sending this to unionfs mailinglist too so people can find it in the
> archive now.
>
>
> Tomas M
> slax.org
>
> Ram Kumar wrote:
> > Hi,
> > I could sucessfully boot into a union which is created by
> > merging two of my hard drive partitions (containing a readonly root
> > file system in one and a empty readwrite partion in other). This is
> > handled by linuxrc script located in my initrd image whose only
> > purpose is to create a union and pivot_root into the new rootfs. Now
> > Iam wondering whether there is a proper way to free the resources
> > (from my embedded linux target) by umounting the initrd image before
> > init is launched. Is this possible ?
> > regards.
> > ram.
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > unionfs mailing list
> > unionfs at mail.fsl.cs.sunysb.edu
> > http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.fsl.cs.sunysb.edu/pipermail/unionfs/attachments/20060317/b8d57443/attachment-0002.htm
More information about the unionfs
mailing list