From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Strange ZFS 'geometry' and error TASK ERROR: zfs error: cannot mount 'zp0/subvol-150-disk-0': no mountpoint set
Date: Fri, 13 Jan 2023 16:30:27 +0100 [thread overview]
Message-ID: <h1a89j-4pn1.ln1@hermione.lilliput.linux.it> (raw)
Stituation: a dedicated server on OVH, installed PVE via the bultn 'cloud
init' procedure.
Created a partition for OS (normal RAID, ext4) and created a RAIDZ1 with
another tw partition.
Pool is now:
root@artemis:~# zpool status
pool: zp0
state: ONLINE
status: Some supported and requested features are not enabled on the pool.
The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
scan: scrub repaired 0B in 00:00:09 with 0 errors on Sun Jan 8 00:24:10 2023
config:
NAME STATE READ WRITE CKSUM
zp0 ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
wwn-0x500a07512f224d2e-part5 ONLINE 0 0 0
wwn-0x500a07512f46109c-part5 ONLINE 0 0 0
errors: No known data errors
(ok, i've to do a 'zpool upgrade' also...). Then created a storage:
zfspool: local-zfs
pool zp0
content rootdir,images
sparse 1
then created some VMs, with no trouble at all. Now i'm trying to create
(really, restore) some LXC and i got the error on subject:
TASK ERROR: zfs error: cannot mount 'zp0/subvol-150-disk-0': no mountpoint set"
Effectivaly:
root@artemis:~# zfs list -o name,mounted,mountpoint
NAME MOUNTED MOUNTPOINT
zp0 no none
zp0/vm-100-disk-0 - -
zp0/zd0 yes legacy
so the 'zp0' fs does not have a mountpoint; it suffices to create one and
reboot?
Thanks.
--
Giuseppe - E pensare che vivrà solo 33 anni...
Maria - Beh, per essere un palestinese è già tanto! (Ellekappa)
next reply other threads:[~2023-01-13 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 15:30 Marco Gaiarin [this message]
2023-01-15 16:14 ` Marco Gaiarin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=h1a89j-4pn1.ln1@hermione.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.