From: Dave Chinner <david@fromorbit.com>
To: Leslie Rhorer <lrhorer@mygrande.net>
Cc: xfs@oss.sgi.com
Subject: Re: Corrupted files
Date: Wed, 10 Sep 2014 15:23:03 +1000 [thread overview]
Message-ID: <20140910052303.GB27048@dastard> (raw)
In-Reply-To: <540FD8DE.7090306@mygrande.net>
On Tue, Sep 09, 2014 at 11:51:42PM -0500, Leslie Rhorer wrote:
> On 9/9/2014 10:33 PM, Dave Chinner wrote:
> >On Tue, Sep 09, 2014 at 10:10:45PM -0500, Leslie Rhorer wrote:
> >>On 9/9/2014 8:53 PM, Dave Chinner wrote:
> >>>On Tue, Sep 09, 2014 at 08:12:38PM -0500, Leslie Rhorer wrote:
> >>>>On 9/9/2014 5:06 PM, Dave Chinner wrote:
> >> I've never used git on a package maintained in my distro. Will I
> >>have issues when I upgrade to Debian Jessie in a few months, since
> >>this is not being managed by apt / dpkg? It looks like Jessie has
> >>3.2.1 of xfs-progs.
> >
> >If you're using debian you can build debian packages directly from
> >the git tree via "make deb" (I use it all the time for pushing
> >new builds to my test machines) and so when you upgrade to Jessie it
> >should just replace your custom built package correctly...
>
> Thanks a ton, Dave (and everyone else who helped). That seems to
> have worked just fine. The three grunged entries are gone and the
> system is happily copying over the backups. Now I'll run another
> rsync with checksum to make sure everything is good before putting
> the backup into production. I'm also going to upgrade the
> controller BIOS just in case.
Good to hear. Hopefully everything will check out. Just yell if you
need more help. ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-10 5:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 15:21 Corrupted files Leslie Rhorer
2014-09-09 15:50 ` Sean Caron
2014-09-09 16:03 ` Sean Caron
2014-09-09 22:24 ` Eric Sandeen
2014-09-09 22:57 ` Sean Caron
2014-09-10 1:00 ` Roger Willcocks
2014-09-10 1:23 ` Leslie Rhorer
2014-09-10 5:09 ` Eric Sandeen
2014-09-10 0:48 ` Leslie Rhorer
2014-09-10 1:10 ` Roger Willcocks
2014-09-10 1:31 ` Leslie Rhorer
2014-09-10 14:24 ` Emmanuel Florac
2014-09-10 14:49 ` Sean Caron
2014-09-09 16:08 ` Emmanuel Florac
2014-09-09 22:06 ` Dave Chinner
2014-09-10 1:12 ` Leslie Rhorer
2014-09-10 1:25 ` Sean Caron
2014-09-10 1:43 ` Leslie Rhorer
2014-09-10 14:31 ` Emmanuel Florac
2014-09-10 14:52 ` Grozdan
2014-09-10 15:12 ` Emmanuel Florac
2014-09-10 15:32 ` Grozdan
2014-09-10 14:54 ` Sean Caron
2014-09-10 23:18 ` Leslie Rhorer
2014-09-11 13:24 ` Greg Freemyer
2014-09-12 7:06 ` Emmanuel Florac
2014-09-10 1:53 ` Dave Chinner
2014-09-10 3:10 ` Leslie Rhorer
2014-09-10 3:33 ` Dave Chinner
2014-09-10 4:14 ` Leslie Rhorer
2014-09-10 4:22 ` Leslie Rhorer
2014-09-10 14:34 ` Emmanuel Florac
2014-09-10 4:51 ` Leslie Rhorer
2014-09-10 5:23 ` Dave Chinner [this message]
2014-09-11 5:47 ` Leslie Rhorer
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=20140910052303.GB27048@dastard \
--to=david@fromorbit.com \
--cc=lrhorer@mygrande.net \
--cc=xfs@oss.sgi.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