On Thu, Jun 01, 2023 at 06:15:35AM +0800, Jazzi Hong wrote:
> Fixed, thanks Otto. I checked this drive and found an error of "BAD
> SUPER BLOCK: MAGIC NUMBER WRONG", it's fixed in the end. So I changed
> the last option of the fstab file from ZERO to TWO thus the command
> fsck can check it automa
Fixed, thanks Otto. I checked this drive and found an error of "BAD
SUPER BLOCK: MAGIC NUMBER WRONG", it's fixed in the end. So I changed
the last option of the fstab file from ZERO to TWO thus the command
fsck can check it automatically. Thank you all for the great help, I
am so happy my little NA
On Wed, May 31, 2023 at 10:25:06PM +0800, Jazzi Hong wrote:
> Thanks for all the help. Hereby is the result of command `disklabel
> sd0`, seems the drive is well detected by failed mounted:
>
> > $ doas disklabel sd0
> # /dev/rsd0c:
> type: SCSI
> disk: SCSI disk
> label: SAMSANG ST1000LM
> duid:
Thanks for all the help. Hereby is the result of command `disklabel
sd0`, seems the drive is well detected by failed mounted:
> $ doas disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: SAMSANG ST1000LM
duid: 2b6c2b5b929f9a55
16 partitions:
#size offset fstyp
On Wed, May 31, 2023 at 11:21:15AM +0100, Zé Loff wrote:
> On Wed, May 31, 2023 at 05:25:07PM +0800, Jazzi Hong wrote:
> > You made the point, thank you Maksim.
> > I checked /mnt/hdd and nothing there.
> > > # cat /etc/fstab
> > 1593ab2ee369c420.b none swap sw
> > 1593ab2ee369c420.a / ffs rw 1 1
On Wed, May 31, 2023 at 05:25:07PM +0800, Jazzi Hong wrote:
> You made the point, thank you Maksim.
> I checked /mnt/hdd and nothing there.
> > # cat /etc/fstab
> 1593ab2ee369c420.b none swap sw
> 1593ab2ee369c420.a / ffs rw 1 1
> 1593ab2ee369c420.e /var ffs rw,nodev,nosuid 1 2
> 2b6c2b5b929f9a55.i
On Wed, May 31, 2023 at 05:25:07PM +0800, Jazzi Hong wrote:
> You made the point, thank you Maksim.
>
> I checked /mnt/hdd and nothing there.
>
> > # cat /etc/fstab
> 1593ab2ee369c420.b none swap sw
> 1593ab2ee369c420.a / ffs rw 1 1
> 1593ab2ee369c420.e /var ffs rw,nodev,nosuid 1 2
> 2b6c2b5b929
What do you get if you run the below commands? OpenBSD defaults to
using UDP for NFS. Linux I believe defaults to using TCP. I would have
expected a more explicit Portmap error though if it was that.
showmount -e hostname
rpcinfo -t hostname mountd
rpcinfo -u hostname mountd
rpcinfo -t hostname n
You made the point, thank you Maksim.
I checked /mnt/hdd and nothing there.
> # cat /etc/fstab
1593ab2ee369c420.b none swap sw
1593ab2ee369c420.a / ffs rw 1 1
1593ab2ee369c420.e /var ffs rw,nodev,nosuid 1 2
2b6c2b5b929f9a55.i /mnt/hdd ffs rw,noexec,nosuid,nodev 0 0
> # doas sysctl hw.disknames
h
The /mnt/hdd partition on your NFS server might just be not mounted
which does not prevent nfs service from successfully serving an empty
directory.
Or one of your two nfs clients might have deleted all your files and you
did not notice this.
On Wed May 31 09:27:04 2023, Maksim Rodin wrote:
> Hell
Hello,
Silly question but...
Are you sure that your NFS server still has any files on /mnt/hdd?
On Wed May 31 09:07:15 2023, Jazzi Hong wrote:
> Hello,
>
> I have OpenBSD 7.2 installed and NFS service running on Cubieboard2,
> one Linux client and one MacOS client, everything works fine for the
>
Hello,
I have OpenBSD 7.2 installed and NFS service running on Cubieboard2,
one Linux client and one MacOS client, everything works fine for the
last 6 months.
Yesterday as usual I mounted NFS share and showed mounting
successfully even command `df -h` got it, but `ls /Users/jazzi/nfs`
showed not
12 matches
Mail list logo
