xfs
[Top] [All Lists]

Re: [RFC 11/32] xfs: convert to struct inode_time

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [RFC 11/32] xfs: convert to struct inode_time
From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
Date: Mon, 2 Jun 2014 09:09:23 +0200
Cc: Nicolas Pitre <nicolas.pitre@xxxxxxxxxx>, Arnd Bergmann <arnd@xxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Linux-Arch <linux-arch@xxxxxxxxxxxxxxx>, "Joseph S. Myers" <joseph@xxxxxxxxxxxxxxxx>, John Stultz <john.stultz@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Ley Foon Tan <lftan@xxxxxxxxxx>, Linux FS Devel <linux-fsdevel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=/2hw/2jKf7vgl31+I5DSvbTjvhNBtD1+rBnYM+4otw8=; b=dwZRbgD1TheRGKEn1WXJP4GfBFE5WC0gMPtXKVEHit0UrBQ+cmcJf8p9HZUfJXsNYQ HxPbE9Y0RwMQKK1gv7uPXzN1FoV8osdnW3GgNP9BZoPYxtGet+TgTvxI7tkXN3gHyTFV JsGzS66VEXT7UtKhSgoaXCnEmFoQ2K5NL9fv9pmAsKCMtUckzJCNq+If30dRbaxQaBmO B4daQZV+WxryejX4ue44H5KvxNT1ABg7riRIzOTidHf2ZAfM0EIqq4xSlUtLTfirDCwe 8jI1oIwbIJDCDvO8stSF73DXNl0wCW4UTbh7Kyae1wfx3yVAqlg+KnluuFwtgN1ZL19a a35w==
In-reply-to: <20140602022211.GN6677@dastard>
References: <1401480116-1973111-1-git-send-email-arnd@xxxxxxxx> <538995D4.9050702@xxxxxxxxx> <alpine.LFD.2.11.1405311055410.17310@xxxxxxxxxxx> <8618458.1EVJCoVbkH@wuerfel> <alpine.LFD.2.11.1406012121430.17310@xxxxxxxxxxx> <20140602022211.GN6677@dastard>
Sender: geert.uytterhoeven@xxxxxxxxx
On Mon, Jun 2, 2014 at 4:22 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> Filesystems place all sorts of userspace visible limits on storage -
> ever tried to create a file >16TB on ext4? The on-disk format
> doesn't support it, so it returns an out of range error (E2BIG, I
> think) if you try. XFS, OTOH, handles this just fine and so it
> continues to work. It's exactly the same with timestamps - there's a
> physical limit to what can sanely be stored in any given filesystem
> and it's an *error condition* to go beyond that limit....

This comparison doesn't fly.
File sizes do not depend on the current time (except for the increase of
megapixels in your new camera ;-).
Writing a 15 GiB file to ext4 is not something that magically stops working
tomorrow.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

<Prev in Thread] Current Thread [Next in Thread>