From: "J.H." <warthog9@kernel.org>
To: users@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kernel.org users] [KORG] Master / hera upgrade & downtime announcement
Date: Tue, 02 Nov 2010 11:18:56 -0700 [thread overview]
Message-ID: <4CD05610.2000108@kernel.org> (raw)
In-Reply-To: <4CCF4AB3.8070505@kernel.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Latest update
> I'm going to do a full resync of /pub - this will squash anything that
> was there with what was present around 1900 UTC on Nov 1st. Home dirs,
> mail, etc are going to have to get dealt with on a per-case basis.
/pub was reset last night, which basically means anything that may have
been pushed from about 19:00 Nov 1 UTC to 02:56 Nov 2 UTC could be
squashed and will need to be re-pushed, but this should clean up the
vast majority of the issues there were present there.
This will likely mean a few more extra tip e-mails for those of you on
that mailing list (again sorry about that), and possibly some other
e-mails from various cron scripts that individual users are running and
maintaining.
> I might just setup an NFS mount across the two machines and let people
> snag what they need on their own with respect to that.
I've gone ahead and created /home/restore - it has have a copy of the
home directory as it existed around 19:00 Nov 1 UTC. I will garauntee
it being around until Nov 30th. I will need to delete it sometime after
that, mainly because of the backup bloat it will cause. If you made
changes to your home directory between Sept. 29th and Nov 1, you will
need to deal with the merging of the data manually.
With respect to those users who use IMAP against the machine I've copied
your INBOX mail spools to /home/restore/MAILSPOOL. The easiest way to
deal with merging this in with your current inbox is toe copy your spool
to your ~/mail directory, load up thunderbird and copy all the mail from
the old inbox to your current inbox and then use something like "Remove
Duplicate Messages (alternate)" to eliminate the duplicates.
That should be everything. I'm going to keep poking around trying to
find anything else that's off kilter, but I haven't seen any new reports
of anything else amiss yet and things seem to be working otherwise. So
if you see something amiss, please let me know ASAP.
- - John 'Warthog9' Hawley
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkzQVhAACgkQ/E3kyWU9dic1ZwCeL0IdwITS2lYcmQhmOK/kevk5
l2wAnAzfynrADpgv+I7KL0rvQQU8Fmxe
=6g1w
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-11-02 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 20:40 [KORG] Master / hera upgrade & downtime announcement J.H.
2010-10-29 21:04 ` [kernel.org users] " Steven Rostedt
2010-10-30 4:35 ` "Singapore Citizen Mr. Teo En Ming (Zhang Enming) 张恩鸣 "
2010-11-01 20:37 ` [kernel.org users] " J.H.
2010-11-01 22:09 ` J.H.
2010-11-01 23:18 ` J.H.
2010-11-02 18:18 ` J.H. [this message]
2011-01-12 19:04 ` J.H.
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=4CD05610.2000108@kernel.org \
--to=warthog9@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=users@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