linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@lcse.umn.edu>
To: Klaus Strebel <stb@ep-ag.com>
Cc: linux-raid@vger.rutgers.edu, linux-lvm@msede.com, gfs-devel@lcse.umn.edu
Subject: [linux-lvm] Re: PATCH: volume drivers in ll_rw_block
Date: Tue, 10 Aug 1999 14:39:41 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.9908101134520.14241-100000@orinoco.lcse.umn.edu> (raw)
In-Reply-To: <37AFFA45.FAF773E@ep-ag.com>

> the lvm_map-0.7 lacks one thing in ll_rw_blk.c, i show below in
> generic_map-2.2.10-raid what and where.

> -#if defined CONFIG_BLK_DEV_LVM || defined CONFIG_BLK_DEV_LVM_MODULE
> -                major = MAJOR(bh[i]->b_dev);
> -                if ( major == LVM_BLK_MAJOR) {
> -                   int ret;
> -
> -                   if ( lvm_map_ptr == NULL) {
> -                              printk ( KERN_ERR
> -                               "Bad lvm_map_ptr in ll_rw_block\n");
> -                      goto sorry;
> -                   }
> -                   if ( ( ret = ( lvm_map_ptr) ( MINOR ( bh[i]->b_dev),
> -                                                 &bh[i]->b_rdev,
> -                                                 &bh[i]->b_rsector,
> -                                                 bh[i]->b_size >> 9,
> -                                                 rw)) != 0) {
> -                      printk ( KERN_ERR
> -                               "Bad lvm_map in ll_rw_block\n");
> -                      goto sorry;
> -                   }
> -                   /* remap major too ... */
> -                   major = MAJOR(bh[i]->b_rdev);
> -               }
> -#endif


Correct.  This chunk is no longer needed.  In the lvm_map-0.7 patch I
wasn't trying to fix everything from patch-2.2.10-LVM, only lvm.c.

To adhere with the generic mapping, patch-2.2.10-LVM should change in the
following ways:

 - remove all modifications to the function ll_rw_block()
 - remove all references to lvm_map from ll_rw_blk.c
 - lvm.c should include the changes in lvm_map-0.7

In other words, when using the generic mapping, the LVM stuff shouldn't
affect ll_rw_blk.c at all except the insertion of lvm_init at the very
end.  This simplifies the LVM patch.

Thanks for pointing that out.  I'm not sure if this addresses your fsck
problem or not.

David Teigland

      reply	other threads:[~1999-08-10 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-09 19:52 [linux-lvm] PATCH: volume drivers in ll_rw_block David Teigland
1999-08-10 10:09 ` Klaus Strebel
1999-08-10 19:39   ` David Teigland [this message]

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=Pine.LNX.4.10.9908101134520.14241-100000@orinoco.lcse.umn.edu \
    --to=teigland@lcse.umn.edu \
    --cc=gfs-devel@lcse.umn.edu \
    --cc=linux-lvm@msede.com \
    --cc=linux-raid@vger.rutgers.edu \
    --cc=stb@ep-ag.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;
as well as URLs for NNTP newsgroup(s).