Date: Mon, 3 Jun 2024 18:45:46 -0400 From: William Dudley <wfdudley@gmail.com> Cc: questions@freebsd.org Subject: Re: help with full zfs "partitions" - can't delete files - SOLVED? Message-ID: <CAFsnNZL1QK6eF%2BZ9oGoMKh_aOj7nqdb%2Bs%2BnbGXeZZe3qU1jj7w@mail.gmail.com> In-Reply-To: <PH0PR11MB477658D89A6BB6959AB24E89E6FF2@PH0PR11MB4776.namprd11.prod.outlook.com> References: <CAFsnNZKH0A8FztcB9Ntq3CJK0jF1oAhgH02eJjds56s3-JAmFQ@mail.gmail.com> <PH0PR11MB477658D89A6BB6959AB24E89E6FF2@PH0PR11MB4776.namprd11.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] see below On Mon, Jun 3, 2024 at 6:31 PM Edward Sanford Sutton, III < mirror176@hotmail.com> wrote: > On 6/3/24 13:28, William Dudley wrote: > > The problem: > > > > FreeBSD 13.3 amd64 system, with > > a zfs pool built from two physical drives. > > Mirrored or striped layout? > Striped > > > The zfs pool has 7 "partitions" (is that what they're called?) > > > > I was copying files over from another machine and didn't realize that > > I filled one of the partitions. > > What user? What command(s)? > as root, by doing rsync from another machine's disk that is an NFS mount. > > > I can't proceed now with this one full partition. > > If the pool is full, all datasets on it should be impacted instead of > just one. > > > Every single command fails due to "out of space". > > > > That includes: > > rm (one file or many) > > dd if=/dev/zero of=(some file) > > truncate (somefile) > > zfs destroy poolname/partitionname > > cannot destroy 'poolname/partitionname': out of space > > Tried as root? Users are limited from filling a partition fully. I > thought ZFS always forces a certain amount be free to avoid issues like > being unable to COW write to delete data. > All commands as root. > > > There are no snapshots, I never created any. > > > > Extensive googling has not shown any more than bug reports acknowledging > > that this is a problem. > > > > How do I fix this, short of burning the machine to the ground and > > starting over? > > > > Thanks, > > Bill Dudley > > > > This email is free of malware because I run Linux. > > No system, Linux included, can guarantee that. I have Linux malware > infested botnets reaching out to me every day though 'usually' not by > email. > I know, but it's "mostly" true, compared to people running Winders. ANYWAY, this might be "solved", in the sense that I have a work around. Paul Procacci emailed me a suggestion to try this: sysctl -w vfs.zfs.spa.slop_shift=6 and if that doesn't work, try 7 or 8. A setting of 7 allows me to delete files. Not sure if this lets me fully clean up the mess, but so far, so good. Bill Dudley [-- Attachment #2 --] <div dir="ltr"><div dir="ltr">see below<br clear="all"><div><div dir="ltr" class="gmail_signature gmail-show"><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 3, 2024 at 6:31 PM Edward Sanford Sutton, III <<a href="mailto:mirror176@hotmail.com">mirror176@hotmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 6/3/24 13:28, William Dudley wrote:<br> > The problem:<br> > <br> > FreeBSD 13.3 amd64 system, with<br> > a zfs pool built from two physical drives.<br> <br> Mirrored or striped layout?<br></blockquote><div><br></div><div>Striped </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> > The zfs pool has 7 "partitions" (is that what they're called?)<br> > <br> > I was copying files over from another machine and didn't realize that<br> > I filled one of the partitions.<br> <br> What user? What command(s)?<br></blockquote><div><br></div><div>as root, by doing rsync from another machine's disk that is an NFS mount. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> > I can't proceed now with this one full partition.<br> <br> If the pool is full, all datasets on it should be impacted instead of <br> just one.<br> <br> > Every single command fails due to "out of space".<br> > <br> > That includes:<br> > rm (one file or many)<br> > dd if=/dev/zero of=(some file)<br> > truncate (somefile)<br> > zfs destroy poolname/partitionname<br> > cannot destroy 'poolname/partitionname': out of space<br> <br> Tried as root? Users are limited from filling a partition fully. I <br> thought ZFS always forces a certain amount be free to avoid issues like <br> being unable to COW write to delete data.<br></blockquote><div><br></div><div>All commands as root. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> > There are no snapshots, I never created any.<br> > <br> > Extensive googling has not shown any more than bug reports acknowledging<br> > that this is a problem.<br> > <br> > How do I fix this, short of burning the machine to the ground and <br> > starting over?<br> > <br> > Thanks,<br> > Bill Dudley<br> > <br> > This email is free of malware because I run Linux.<br> <br> No system, Linux included, can guarantee that. I have Linux malware <br> infested botnets reaching out to me every day though 'usually' not by email.<br></blockquote><div><br></div><div>I know, but it's "mostly" true, compared to people running Winders.</div><div><br></div><div>ANYWAY, this might be "solved", in the sense that I have a work around.</div><div>Paul Procacci emailed me a suggestion to try this:<br></div><div><font face="monospace">sysctl -w vfs.zfs.spa.slop_shift=6</font><br></div><div>and if that doesn't work, try 7 or 8. A setting of 7 allows me to delete files.</div><div>Not sure if this lets me fully clean up the mess, but so far, so good.</div><div><br></div><div>Bill Dudley </div></div></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFsnNZL1QK6eF%2BZ9oGoMKh_aOj7nqdb%2Bs%2BnbGXeZZe3qU1jj7w>