YAFFS team,<div><br></div><div>After investigating some corrupt files in our Android app, I think I&#39;ve narrowed the problem down to YAFFS. The same code on a FAT fs performs as expected.</div><div><br></div><div>First, it looks like RandomAccessFile.setLength(), which translates to ftruncate(), can fail silently. For example, I can set the file length to much more space than is available, and I don&#39;t get an error. I&#39;m not sure why else ftruncate() fails, but we&#39;ve seen cases where the actual file length (as reported by &quot;ls -l&quot;) is less than it should be. RandomAccessFile.length(), which seeks to the end of the file, returns the requested value, which is much longer than the available space. I even tried writing and reading the last byte, and I still didn&#39;t get an error.</div>

<div><br></div><div>Finally, File.length(), which uses stat, returns 0 for the length, and the available space reported by &quot;df&quot; doesn&#39;t go down. :-(</div><div><br></div><div>As a workaround, I&#39;m going to append bytes to the end of the file instead of using ftruncate(), but I thought I should bring these issues to your attention.</div>

<div><br></div><div>Thanks,</div><div>Bob</div><div><br></div>