All of lore.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: "Bryn M. Reeves" <breeves@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 2.6.20] updated dm-loop patch
Date: Thu, 15 Feb 2007 23:30:57 +0100	[thread overview]
Message-ID: <1629339771@web.de> (raw)

hi again, 

just wondering - would it make sense to have dm-loop supporting partitions "out of the box" ?

i gave it a try, but the appropriate ioctls seem to be missing.

Command (m for help): p

Disk /dev/mapper/loop0: 104 MB, 104857600 bytes
255 heads, 63 sectors/track, 12 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

             Device Boot      Start         End      Blocks   Id  System
/dev/mapper/loop0p1               1           6       48163+  83  Linux
/dev/mapper/loop0p2               7          12       48195   83  Linux

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.


fdisk providing wrong information here, because removing and re-adding loop0 doesn`t make loop0p1 or loop0p2 appear.

there is some nice script at http://www.ussg.iu.edu/hypermail/linux/kernel/0307.2/0935.html which makes those partitions available by creating additional devices, but i`m just wondering if this could work automa(t|g)ically.

regards
roland




> -----Ursprüngliche Nachricht-----
> Von: "Bryn M. Reeves" <breeves@redhat.com>
> Gesendet: 15.02.07 13:28:24
> An: devzero@web.de
> CC: device-mapper development <dm-devel@redhat.com>
> Betreff: Re: [dm-devel] [PATCH 2.6.20] updated dm-loop patch


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> devzero@web.de wrote:
> > Hi Bryn, 
> > 
> > with this patch and also with 0.415 i have the following problem when compiling it with stock 2.6.20 :
> > 
> >   Building modules, stage 2.
> >   MODPOST 1 modules
> > WARNING: "invalidate_mapping_pages" [drivers/md/dm-loop.ko] undefined!
> > make[1]: *** [__modpost] Error 1
> > make: *** [modules] Error 2
> > 
> > i found , that this was due to missing 
> > 
> > EXPORT_SYMBOL(invalidate_mapping_pages);
> > 
> > in mm/truncate.c 
> > 
> > i found 
> > http://lkml.org/lkml/2007/1/3/154
> > 
> > it looks that this didn`t go into 2.6.20 and we need at least 2.6.20-git11 ?
> > changelog at http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.20-git11.log telling that it had just had been merged on 10th of february:
> > 
> 
> Hi Roland,
> 
> That's right - I keep my git tree fairly close to upstream, so as soon
> as the patch that deprecated invalidate_inode_pages was merged, I
> converted dm-loop to use invalidate_mapping_pages instead.
> 
> This means that dm-loop will build without warnings on the latest
> kernel.org tree but it does mean that you will need the additional patch
> you referenced if you want to apply it to a plain 2.6.20 kernel.
> 
> Kind regards,
> 
> Bryn.
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> 
> iD8DBQFF1FHa6YSQoMYUY94RAl2iAKDAlrTqxDCNP7i/bhexl6JJGW1rNwCgksXz
> 5limiJOmDRoBKdHDUsU0pFE=
> =HwdH
> -----END PGP SIGNATURE-----
> 


_______________________________________________________________________
Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=022222

             reply	other threads:[~2007-02-15 22:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 22:30 devzero [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-15 11:45 [PATCH 2.6.20] updated dm-loop patch devzero
2007-02-15 12:28 ` Bryn M. Reeves
2007-02-21  0:14   ` roland
2007-02-12  8:49 roland
2007-02-12 15:24 ` Bryn M. Reeves
2007-02-06 11:35 Bryn M. Reeves
2007-02-13 20:20 ` Bryn M. Reeves
2007-02-15  0:51   ` Bryn M. Reeves

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=1629339771@web.de \
    --to=devzero@web.de \
    --cc=breeves@redhat.com \
    --cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.