New answers tagged

0

Answering your plane question: it would be 1) combine multiple phisical devices into a volume group. pvcreate /dev/sdb1 /dev/sdb2 2) create a Volume Group vgcreate NameofVG /dev/sdb1 /dev/sdb2 -- Now you can see the vg created by using vgdisplay 3) create a Logical Volume lvcreate -n NAME -L 20G NameofVG 4) making filesystem to it. (xfs for example) ...


1

I have fixed this issue, but the resolution is unsatisfactory. However, I post it here incase it helps anyone else. It appears that the dataset was never successfully mounted. This is apparent from the df listing. I tried mounting the drive manually using sudo zfs mount -v zstorage/movies This for reasons I cannot discern took about 5 minutes to ...


1

You should have done a copy-paste instead of a screenshot :) Here's what it looks like: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T O disk |-sda1 8:1 0 1004.5K O part |-sda2 8:2 0 19.5G O part / |-sda3 8:3 0 1.8T O part /home \-sda4 8:4 0 15.6G O part [SWAP] sdb 8:16 0 1.8T O disk You'...


0

LVM: no need to partition /dev/sdb create PV of /dev/sdb create VG with /dev/sdb create LV on VG format LV mount LV in temporary location copy /home to temporary location umount LV umount /home mount LV to /home make PV of /dev/sda3 add sda3 PV to VG resize /home LV resize /home filesystem voila!


0

try running fdisk -l just to make sure /def/sdf is the actual block name, so probably it should mount with: sudo mount /dev/sdf1 /vol-a


11

BINGO!!! Alright, here is how this was resolved: I referenced this artice for unmounting the datastore, https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004605 Step 1: Manually unmount the datastore from the host with this command: esxcli storage filesystem unmount [-u UUID | -l label | -p path ] In ...


5

This tip worked for me in the past, if you can disable ATS-Only: Cannot mount the VMFS5 datastore when using storage encryption appliances (2030416) I guess no VM are up in your case, but they need to be close to be able to run the command. Some storage encryption appliances may block certain SCSI commands, including ATS commands, sent from ESXi ...


0

It turns out there was a bug in quotacheck. I submitted a patch to fix it, but have no clue when (or even if) a new version of quota including that patch will be published. Directly attaching files to my answer does not seem to be possible, so I will not post the patch here. But if someone is interested, make a comment and I will post the patch as a code ...


0

It is possible... sort of. This is a high-level overview. Mount the specific filesystem that you want to access as a ready only mount. You need to use the "-o union" option (more on this later). Next you will need either another read-write device, or you will need something like bindFS to map a scratch folder. http://bindfs.org/ With the second mount point,...


0

kpartx works only with raw (uncompressed) images. To mount any image supported by libvirt use guestmount(1): guestmount -a IMAGE MOUNTPOINT


0

Based on a flickerdfly's answer, influenced by a comment from WhiteKnight Create a detector function the fly. eval "function is_readonly () { $( grep -P "\sro[\s,]" /proc/mounts | awk '{print "if echo $1 | grep -q \""$2"\"; then return 0;fi"}' ) return 1;}"; use it to determine if a path is on a read only fs is_readonly /path/to/file/...


0

mkfs.xfs (starting with version 3.2.4 of xfsprogs) recently defaulted to version 5 superblock, with lots of new enhancements like metadata CRC checksums. Version 5 superblock requires a 3.16 kernel or better. This error is typical, you're trying to mount the volume on a kernel which doesn't support v5 superblocks, i. e. with a version prior to 3.16. Be ...


0

again with comment thing - not being able to put comments due to 50 points is killing me. But to give you short answer. It's not possible. if you set it up only to read then you can't expand/add/create from this device. Since it's still operating on "file level" then it cannot allocate any space on it, therefore it can't be treated as FS in any matter.


0

I'm hoping you created filesystems after you defined the partitions. I'm assuming ext4? Anyway, the cciss CHECK CONDITION errors in dmesg indicate an array failure. I know this is Arch, so HP support is pretty poor, but can you see if you can install hpssacli or hpacucli? I'd like to see the output of: hpacucli ctrl all show config and hpacucli ctrl ...


0

My work around was to systemctl enable docker.service and then create a /etc/systemd/system/docker.service.wants and symlink the media-esdata.mount in to that folder. Systemd was willing to start docker.service on boot and using the folder wants it forced the drive to be mounted. Now I have docker running without having SSH in to the box and run docker (...


0

You will need to "enable" this unit, which means it starts on boot. You can do this via cloud-config or manually with sudo systemctl enable media-esdata.mount


0

You have a very interesting problem. It looks there isn't any option for quotacheck to ignore the directories. Probably you will need to change the quotacheck job and run it for each volume ignoring the binded ones. You can get the list of binded volumes with findmnt with something like: findmnt | awk '$2 ~ /\[.*\]$/' So probably your cron job could be ...


0

Turns out the image was in fact too large. I had a 3 GB image, with only 500 MB of RAM. After resizing the image to 400 MB, I was able to get past this error screen, and also eventually boot my image.


1

Posting the solution that worked for me as I did not find this else where..... First checked the dmesg to see the actual error dmesg | tail and found the error with duplicate UUID [180875.598481] XFS (xvdf2): Filesystem has duplicate UUID 379de64d-ea11-4f5b-ae6a-0aa50ff7b24d - can't mount [180970.058345] XFS (xvdf2): Filesystem has duplicate UUID ...



Top 50 recent answers are included