public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dennis Ullrich <dennis1ullrich@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Kernel Live Patch...
Date: Fri, 08 May 2015 20:04:37 +0200	[thread overview]
Message-ID: <554CFAB5.6050004@gmx.de> (raw)

Dear all,

I want to make a proposal which is similar to online kernel patching 
without reboot... The idea is to do something which could work similar 
to the live kernel patching method. I don't know how difficult it would 
be, to implement my proposal, but here it comes.

For example I have a HDD with one partiton and a Oracle DB on the ext4 
filesystem. I want to migrate it live to another storage (for example a 
LPFC LUN via Multipath) with all processes etc. on the FS.
My idea is to modify the IOStack that it is able to make a "bitwise" 
copy and "simply" move the Filesystem to its new place on a blockdevice.
The point is, to have control about the copy-progress and tell the 
IOStack which device is to use for the requested data, on every access. 
When the copy is done, the admin should be able to remove the old drive. 
All processes should be on the new blockdevice after the movement.

What do you think about this idea?


Best regards,
Dennis

P.S. I know that there are solutions (md, lvm) to do this, if its 
configured in the first place. But you will need a downtime for the 
final switch between new and old (because of the processes).
But in this case I really mean a function which is independent from any 
partiton table, filesystem etc.
and works only on blockdevices.

             reply	other threads:[~2015-05-08 18:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 18:04 Dennis Ullrich [this message]
2015-05-08 18:27 ` Kernel Live Patch Richard Weinberger

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=554CFAB5.6050004@gmx.de \
    --to=dennis1ullrich@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    /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