<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Filesystems on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/filesystems/</link><description>Recent content in Filesystems on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Sat, 15 Feb 2020 11:49:03 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/filesystems/index.xml" rel="self" type="application/rss+xml"/><item><title>Unix's /usr split and standards (and practice)</title><link>http://karpoke.ignaciocano.com/2020/02/15/unix-s-usr-split-and-standards-and-practice/</link><pubDate>Sat, 15 Feb 2020 11:49:03 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/02/15/unix-s-usr-split-and-standards-and-practice/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Unix&amp;rsquo;s /usr split and standards (and practice)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» utcc.utoronto.ca | &lt;a href="https://utcc.utoronto.ca/~cks/space/blog/unix/UsrSplitAndStandards"&gt;utcc.utoronto.ca&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Stable Linux kernel hit by ext4 data corruption bug</title><link>http://karpoke.ignaciocano.com/2012/10/26/stable-linux-kernel-hit-by-ext4-data-corruption-bug/</link><pubDate>Fri, 26 Oct 2012 08:48:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/10/26/stable-linux-kernel-hit-by-ext4-data-corruption-bug/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Linux kernel developer Theodore ”Ted” Ts’o has released a series of
patches for what he has called ”a Lance Armstrong bug” in the kernel,
meaning behaviour that does not trip up tests but nevertheless makes
the kernel work differently than intended. A user had reported a
problem that caused data loss; the kernel developers quickly narrowed
this down to a fault in the ext4 implementation that was introduced
with the release of Linux 3.6.2 just over a week ago. Apparently, the
data corruption bug was hard to track down as it only manifests itself
if a system is rebooted twice in a relatively short period of time.&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>f2fs: introduce flash-friendly file system</title><link>http://karpoke.ignaciocano.com/2012/10/06/f2fs-introduce-flash-friendly-file-system/</link><pubDate>Sat, 06 Oct 2012 13:54:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/10/06/f2fs-introduce-flash-friendly-file-system/</guid><description>&lt;blockquote&gt;
&lt;p&gt;NAND flash memory-based storage devices, such as SSD, eMMC, and SD
cards, have
been widely being used for ranging from mobile to server systems.
Since they are
known to have different characteristics from the conventional
rotational disks,
a file system, an upper layer to the storage device, should adapt to
the changes
from the sketch.&lt;/p&gt;
&lt;p&gt;F2FS is a new file system carefully designed for the NAND flash
memory-based storage
devices. We chose a log structure file system approach, but we tried
to adapt it
to the new form of storage. Also we remedy some known issues of the
very old log
structured file system, such as snowball effect of wandering tree and
high cleaning
overhead.&lt;/p&gt;
&lt;p&gt;Because a NAND-based storage device shows different characteristics
according to
its internal geometry or flash memory management scheme aka FTL, we
add various
parameters not only for configuring on-disk layout, but also for
selecting allocation
and cleaning algorithms.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>