Re: [PATCH 2/3] Fix problems on multi-TB filesystem and file

"Takashi Sato" <[email protected]> wrote:
>
>  This is a patch to add blkcnt_t as the type of inode.i_blocks.
>  This enables you to make the size of blkcnt_t either 4 bytes or 8 bytes
>  on 32 bits architecture with CONFIG_LSF.

What was the rationale behind CONFIG_LSF?  It's a bit of an ugly thing and
I'm wondering if we wouldn't be better off just removing it and simply
fixing >2TB support for all .configs?

Do the common userspace tools need to be updated for this, or do they
already get it right?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • RE: [PATCH 2/3] Fix problems on multi-TB filesystem and file
    • From: "Takashi Sato" <[email protected]>

• References:
  • [PATCH 2/3] Fix problems on multi-TB filesystem and file
    • From: "Takashi Sato" <[email protected]>

• Prev by Date: Re: [PATCH 1/3] Fix problems on multi-TB filesystem and file
• Next by Date: Re: [PATCH 3/3] Fix problems on multi-TB filesystem and file
• Previous by thread: [PATCH 2/3] Fix problems on multi-TB filesystem and file
• Next by thread: RE: [PATCH 2/3] Fix problems on multi-TB filesystem and file
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]