From: covici@ccs.covici.com
To: Lionel Bouton <lionel-subscription@bouton.name>
Cc: =?UTF-8?Q?Holger_Hoffst=c3=a4tte?=
<holger.hoffstaette@googlemail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs says no errors, but booting gives lots of errors
Date: Sat, 10 Oct 2015 20:28:59 -0400 [thread overview]
Message-ID: <29851.1444523339@ccs.covici.com> (raw)
In-Reply-To: <5619A615.3090503@bouton.name>
Lionel Bouton <lionel-subscription@bouton.name> wrote:
> Le 11/10/2015 01:32, covici@ccs.covici.com a écrit :
> > [...]
> > I don't know if the file in question had the correct data, I only did a
> > directory listing, but this makes no sense -- I did an rsync just before
> > booting and got all kinds of errors and the only difference is the file
> > system, this is what I am saying.
>
> What makes no sense is that the same filesystem both shows the file is
> there and isn't. If there was data corruption or buggy behaviour at
> least it should be somehow consistent.
> What is more likely is that the rsync was incomplete and didn't transfer
> some data needed by systemd: did you transfer (from the top of my head)
> extended attributes, special files, device files ? By default rsync
> doesn't do that.
The only thing I transferred that was unusual is hard links. Otherwise
it was just
rsync --progress -avhH --numeric-ids followed by the various source
directories root file system to a subvolume rootfs, /usr to a subvolume
called usr, var to a subvolume called var and home to a subvolume
called home. And what is more confusing, I did check the contents of
postgresql.conf and they matched exactly, the one on my ext4 system and
the one on the btrfs file system -- so I don't know why the check
program gave that message. Also, another thing which was not consistent
is that in my first boot mysql service did not start, but it did in
subsequent boots. Now, I did not transfer anything under /var/run as
its linked to /run, same for /var/lock as its linked to /run/lock.
Device files, I did not transfer anythin specific, I would think udev
would create those under /dev. In this case, I wish I were doing
something dumb, it would not be fun, but at least I could proceed and I
could run with the system.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
next prev parent reply other threads:[~2015-10-11 0:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 12:46 btrfs says no errors, but booting gives lots of errors covici
2015-10-10 14:12 ` Holger Hoffstätte
2015-10-10 14:41 ` covici
2015-10-10 15:46 ` Lionel Bouton
2015-10-10 16:10 ` Holger Hoffstätte
2015-10-10 16:55 ` covici
2015-10-10 22:04 ` Lionel Bouton
2015-10-10 23:02 ` covici
2015-10-10 23:08 ` covici
2015-10-11 12:13 ` Duncan
2015-10-11 12:29 ` covici
2015-10-15 2:10 ` Duncan
2015-10-10 23:21 ` Lionel Bouton
2015-10-10 23:32 ` covici
2015-10-10 23:58 ` Lionel Bouton
2015-10-11 0:28 ` covici [this message]
2015-10-10 16:45 ` covici
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=29851.1444523339@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=holger.hoffstaette@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lionel-subscription@bouton.name \
/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).