Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connectionsPath: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.localhost!not-for-mail From: Grant Edwards Newsgroups: comp.arch.embedded Subject: Re: How do you wipe a UBI filesystem? Date: Wed, 5 Feb 2025 21:15:32 -0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Message-ID: References: Injection-Date: Wed, 5 Feb 2025 21:15:32 -0000 (UTC) Injection-Info: reader2.panix.com; posting-host="localhost:::1"; logging-data="1664"; mail-complaints-to="abuse@panix.com" User-Agent: slrn/1.0.3 (Linux) Bytes: 2067 Lines: 40 On 2025-02-05, Grant Edwards wrote: > Pretend I've got an MTD partition attached as a UBI device. > > That UBI device contains a couple differen UBI volumes. > > In one of those volumes is a UBIFS filesystem that has a bunch of > files in it. > > I've done some googling, but all of the answers are "use > ubiformat". That will wipe the whole device. I just want to > re-initialize one ubifs filesytem in one volume -- not the whole > ubi device. > > How do I wipe that filesystem (set it back to empty). Do I need to > create an empty ubifs "image" file using mkfs.ubifs and then use > ubiupdatevol to write that image to the volume? > > Isn't there a simpler way? I've figured out two other ways to do it: ubiupdatevol -t /dev/ubiX_Y mount -t ubifs /dev/ubiX:volname /mnt/point That works, but apparently that erases every block in the volume. That's a lot of unecessary wear. Surely you can "empty" the filesystem without erasing every block in the volume (when probably 90% of the blocks have never been written). Another option: ubirmvol /dev/ubiX -N volname umimkvol /dev/ubiX -N volname -m mount -t ubifs /dev/ubiX:volname /mnt/point That too seems to work, but modifying the devices volume table/list seems a bit risky compared to simply re-initializing the filesystem inside an existing volume.