Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I can not format the device dev/pmem0 as pmfs #3

Open
BOGEDABUDA opened this issue Aug 11, 2020 · 9 comments
Open

I can not format the device dev/pmem0 as pmfs #3

BOGEDABUDA opened this issue Aug 11, 2020 · 9 comments

Comments

@BOGEDABUDA
Copy link

I am sorry to disturb you that I have met a issues about pmfs-new.
According to the "README.md", after rebooting and inserting the module, we can initialize a PMFS instance with the following command:#mount -t pmfs -o init /dev/pmem0 /mnt/ramdisk
But the Terminal reports that mount: wrong fs type, bad option, bad superblock on /dev/pmem0,missing codepage or helper program, or other error
When I was trying to format the device dev/pmem0 as pmfs, the Terminal reports thatmkfs: failed to execute mkfs.pmfs: No such file or directory.
How can I solve this problem?

@Andiry
Copy link
Contributor

Andiry commented Aug 11, 2020 via email

@BOGEDABUDA
Copy link
Author

BOGEDABUDA commented Aug 12, 2020

@Andiry Thank you for replying. The output of dmesg | grep pmfs -n is as follows:

1633:[ 141.731334] pmfs: loading out-of-tree module taints kernel.
1634:[ 141.731415] pmfs: module verification failed: signature and/or required key missing - tainting kernel
1635:[ 213.974550] pmfs: arch does not have PCOMMIT support
1636:[ 213.974551] pmfs: arch does not have CLWB support
1637:[ 213.974554] pmfs error:
1639:[ 281.873399] pmfs: arch does not have PCOMMIT support
1640:[ 281.873400] pmfs: arch does not have CLWB support
1641:[ 281.873402] pmfs error:
1659:[ 1579.571032] pmfs: arch does not have PCOMMIT support
1660:[ 1579.571033] pmfs: arch does not have CLWB support
1661:[ 1579.571058] pmfs error:

Please refer to the attached file (i.e., dmesg_log.txt) for the complete output of dmesg.
dmesg_log.txt

@Andiry
Copy link
Contributor

Andiry commented Aug 12, 2020 via email

@BOGEDABUDA
Copy link
Author

Thank you for replying. I print out the return code of bdev_dax_supported in "super.c". The output is as follows:
the code of bdev_dax_supported is : 1
The complete output is attached in "new_dmesg_log.txt".
I run pmfs on VM.Is it because my device does not support DAX?
new_dmesg_log.txt

Thanks,
Bo Ding

@Andiry
Copy link
Contributor

Andiry commented Aug 12, 2020 via email

@BOGEDABUDA
Copy link
Author

Thank you for your advices. I would try a bare-metal environment to make it again.

Thanks,
Bo Ding

@BOGEDABUDA
Copy link
Author

I remount it on a bare-metal environment. And it works, thank you.

@towander
Copy link

In Linux kernel 4.19, I meet the same problem "mount: /mnt/ramdisk: wrong fs type, bad option, bad superblock on /dev/pmem0, missing codepage or helper program, or other error." due to does not support DAX.
when"mount -t pmfs -o init /dev/pmem0 /mnt/ramdisk".
Strangely, I was able to run it successfully 2 years ago in another machine, "ret = bdev_dax_supported(sb, PAGE_SIZE);" While still in super.c.

@towander
Copy link

I mount it on a bare-metal environment.
“mount -o dax -t ext4 /dev/pmem0 /mnt/ramdisk”was successed,ensure DAX enabled.
but in super.c, bdev_dax_supported(sb->s_bdev, PAGE_SIZE)==1.
At last, I add code if(ret==1) --ret; And it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants