Mailinglist Archive: opensuse (2459 mails)

< Previous Next >
Re: [opensuse] mv and cpio have new behavior. How do I get the old back?
  • From: Sam Clemens <clemens.sam1@xxxxxxxxx>
  • Date: Tue, 25 Mar 2008 23:41:30 -0400
  • Message-id: <47E9C5EA.1020907@xxxxxxxxx>
Anders Johansson wrote:
On Tue, 2008-03-25 at 20:39 -0600, Boyd Lynn Gerber wrote:
Thanks, that explains it. I should have used ext3 or reiser. The problem
is I had to reboot a machine with 10.2 and 500 GB drives. ext3 has been
doing it's fsck check for 3 hours. I really can not be without my
machines for many hours for the over 3 month fsck check. I have gone back
to reiser on most systems. I guess I have been lucky. I have never had a
data loss(Knock on wood) with reiser. I just do not have 2 more 1TB
drives to change the XFS to reiser. The above makes things very clear.

You're changing file systems just because the mtime gets updated?

What are you doing that makes the mtime so important? Maybe you're using
it incorrectly, and should be using something else instead?

He's using mtime in a reasonable manner.

But XFS is providing an "unreasonable" behavior -- and I'm
an advocate of using XFS.

In light of this, I'm not so sure if I will be quite
so pro-XFS now.

changing the timestamp on . just because .. has changed
is... very shortsighted, and I would consider it a bug.

In any case, you can set the mtime to whatever you want using touch -m,
so you can have your old timestamps back if you want

That's a hassle.


To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >