https://takao.blog/en/tags/storage/Recent content in Storage on Commentary of TakaoHugo -- gohugo.ioenCommentary of TakaoSat, 13 Jun 2026 23:11:50 +0900https://takao.blog/en/web/js-indexeddb-localforage-localstorage/Fri, 20 Feb 2026 00:00:00 +0900https://takao.blog/en/web/js-indexeddb-localforage-localstorage/<img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Replacing LocalStorage: Dynamic IndexedDB wrapper localForage" /><h2 id="introduction">Introduction </h2><p>Client-side storage is a fundamental requirement for modern web applications — offline caches, user preferences, draft data, and session state all need to persist in the browser. For years, <strong>localStorage</strong> has been the simplest go-to solution, but its limitations become painful as applications grow. This article compares localStorage, raw IndexedDB, and the <strong>localForage</strong> wrapper library, providing practical guidance for choosing the right storage engine.</p> <hr> <h2 id="the-limits-of-localstorage">The Limits of localStorage </h2><p>localStorage offers a straightforward synchronous key-value API — <code>setItem(key, value)</code> and <code>getItem(key)</code> — but it comes with hard constraints:</p>https://takao.blog/en/web/proxmox-zfs-storage/Wed, 14 Aug 2024 00:00:00 +0000https://takao.blog/en/web/proxmox-zfs-storage/<img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Proxmox VE ZFS Storage: Pool Setup, Snapshots, and Optimization" /><h2 id="why-zfs-on-proxmox">Why ZFS on Proxmox </h2><p>ZFS brings enterprise-grade features to Proxmox VE: data integrity via checksumming (detects and repairs silent corruption), transparent compression, instant snapshots and clones, and flexible RAID-like pooling. It replaces traditional volume management and filesystem layers with a single, unified stack.</p> <h2 id="creating-a-pool">Creating a Pool </h2><p>A pool is built from virtual devices (vdevs). Common vdev types:</p> <table> <thead> <tr> <th>Vdev type</th> <th>Minimum disks</th> <th>Usable capacity</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td>Mirror</td> <td>2</td> <td>50%</td> <td>Data mirrored across two disks</td> </tr> <tr> <td>RAIDZ1</td> <td>3</td> <td>67%</td> <td>Single parity (max 1 disk failure)</td> </tr> <tr> <td>RAIDZ2</td> <td>4</td> <td>50%</td> <td>Double parity (max 2 failures)</td> </tr> <tr> <td>RAIDZ3</td> <td>5</td> <td>40%</td> <td>Triple parity (max 3 failures)</td> </tr> <tr> <td>Stripe</td> <td>1</td> <td>100%</td> <td>No redundancy (not recommended)</td> </tr> </tbody> </table> <p>Create a mirrored pool:</p>