On Thu, 2005-12-08 at 14:50 +0000, Anton Altaparmakov wrote: > And it breaks applications, too (e.g. du will then report all your files > to be zero size)... That's not a problem. We have our own ->getattr() method, so we can set stat->blocks to the correct value. The only real side effect is therefore that we waste space in the inode. Cheers, Trond - 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/
- References:
- RE: stat64 for over 2TB file returned invalid st_blocks
- From: "Takashi Sato" <[email protected]>
- RE: stat64 for over 2TB file returned invalid st_blocks
- From: Trond Myklebust <[email protected]>
- RE: stat64 for over 2TB file returned invalid st_blocks
- From: Dave Kleikamp <[email protected]>
- RE: stat64 for over 2TB file returned invalid st_blocks
- From: Trond Myklebust <[email protected]>
- RE: stat64 for over 2TB file returned invalid st_blocks
- From: Dave Kleikamp <[email protected]>
- Re: stat64 for over 2TB file returned invalid st_blocks
- From: "Takashi Sato" <[email protected]>
- Re: stat64 for over 2TB file returned invalid st_blocks
- From: Trond Myklebust <[email protected]>
- Re: stat64 for over 2TB file returned invalid st_blocks
- From: Anton Altaparmakov <[email protected]>
- RE: stat64 for over 2TB file returned invalid st_blocks
- Prev by Date: Re: How to enable/disable security features on mmap() ?
- Next by Date: Re: How to enable/disable security features on mmap() ?
- Previous by thread: Re: stat64 for over 2TB file returned invalid st_blocks
- Next by thread: Re: stat64 for over 2TB file returned invalid st_blocks
- Index(es):
 |