Re: lost nfs mount -

2018-07-20 Thread Ed Greshko
On 07/21/18 05:00, Bob Goodwin wrote:
> On 07/20/18 10:54, Ed Greshko wrote:
>> Your mount command doesn't match what is being exported
>>
>> Your client is trying to mount /home/exports   but you've exported 
>> /exports/home.
> .
> Now with the server /etc/exports and /etc/fstab/ and my mount command made to
> agree, it is possible to connect to the NFS4 server again. I'm not certain 
> exactly
> what was corrupted but it looks like all it needed was service nfs restart,
> exportfs alone was not enough.
>
> I would have responded earlier but my system has been down while we cleared 
> the
> rats nest of wiring under my desk that was responsible for the power 
> drop-out,about
> six hours of non-stop effort.

If you had responded earlier I would not have known.  Bedtime in my part of the
world.  :-)

>
> Thanks for the help, 

Welcome.

-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/ZQZDE2CU6U45NAU2LVUZ6ZORUP5FZVXK/


Re: lost nfs mount -

2018-07-20 Thread Bob Goodwin

On 07/20/18 10:54, Ed Greshko wrote:

Your mount command doesn't match what is being exported

Your client is trying to mount /home/exports   but you've exported 
/exports/home.

.
Now with the server /etc/exports and /etc/fstab/ and my mount command 
made to agree, it is possible to connect to the NFS4 server again. I'm 
not certain exactly what was corrupted but it looks like all it needed 
was service nfs restart, exportfs alone was not enough.


I would have responded earlier but my system has been down while we 
cleared the rats nest of wiring under my desk that was responsible for 
the power drop-out,about six hours of non-stop effort.


Thanks for the help,

Bob

--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10  FEDORA-27/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/KD4C7RLFRT57BT5WYAWCEGYWSPAHQ62O/


Re: lost nfs mount -

2018-07-20 Thread Ed Greshko
On 07/20/18 22:41, Bob Goodwin wrote:
> On 07/19/18 19:44, Ed Greshko wrote:
>> Well, there is your problem.   You need to check your /etc/exports file.
> .
> I don't see anything that has changed in /etc/exports, and I have re-copied 
> it, did
> exportfs, and still can't connect. I believe I was told exportfs is all that 
> needs
> to be done after changes?
>
> hmm, so I
>  tried -
> [root@ASRock-J3455M bobg]# service nfs start
> Redirecting to /bin/systemctl start nfs.service
>
> And now I see -
> [root@Box10 bobg]# mount 192.168.1.86:/home/exports  /mnt/testb
> mount.nfs: access denied by server while mounting 192.168.1.86:/home/exports
> When I try to mount it. Before I got nothing, so at least this is different.
>
> And I now see port 2049 -
>
> [root@ASRock-J3455M bobg]# ss -t -l -n
> State Recv-Q Send-Q  Local Address:Port   
>   
> Peer Address:Port
> LISTEN    0 64 0.0.0.0:41739 0.0.0.0:*
> LISTEN    0 128 0.0.0.0:111 0.0.0.0:*
> LISTEN    0 128 0.0.0.0:20048 0.0.0.0:*
> LISTEN    0 128 0.0.0.0:22 0.0.0.0:*
> LISTEN    0 128 127.0.0.1:6010 0.0.0.0:*
> LISTEN    0 128 0.0.0.0:40667 0.0.0.0:*
> LISTEN    0 64 0.0.0.0:2049 0.0.0.0:*
> LISTEN    0 128 [::]:46347 [::]:*
> LISTEN    0 128 [::]:111 [::]:*
> LISTEN    0 128 [::]:20048 [::]:*
> LISTEN    0 64 [::]:38739 [::]:*
> LISTEN    0 128 [::]:22 [::]:*
> LISTEN    0 128 [::1]:6010 [::]:*
> LISTEN    0 64 [::]:2049  [::]:*
>
>
> /etc/exports is presently -
> [root@ASRock-J3455M bobg]# cat /etc/exports
> /exports/home   
> 192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check,fsid=0)
>
> This was working until the power interruption about 24 hours ago.A second 
> computer
> on the same LAN also fails to connect to this server ...
>
> Perhaps a reboot will help? I'll try that next ...
>
>

Your mount command doesn't match what is being exported

Your client is trying to mount /home/exports   but you've exported 
/exports/home.



-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.


signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/EO5IAGHBTWRM53U2IH6FTI5ER3BPH6RZ/


Re: lost nfs mount -

2018-07-20 Thread Bob Goodwin

On 07/19/18 19:44, Ed Greshko wrote:

Well, there is your problem.   You need to check your /etc/exports file.

.
I don't see anything that has changed in /etc/exports, and I have 
re-copied it, did exportfs, and still can't connect. I believe I was 
told exportfs is all that needs to be done after changes?


hmm, so I
 tried -
[root@ASRock-J3455M bobg]# service nfs start
Redirecting to /bin/systemctl start nfs.service

And now I see -
[root@Box10 bobg]# mount 192.168.1.86:/home/exports  /mnt/testb
mount.nfs: access denied by server while mounting 192.168.1.86:/home/exports
When I try to mount it. Before I got nothing, so at least this is different.

And I now see port 2049 -

[root@ASRock-J3455M bobg]# ss -t -l -n
State Recv-Q Send-Q  Local 
Address:Port  Peer Address:Port

LISTEN    0 64 0.0.0.0:41739 0.0.0.0:*
LISTEN    0 128 0.0.0.0:111 0.0.0.0:*
LISTEN    0 128 0.0.0.0:20048 0.0.0.0:*
LISTEN    0 128 0.0.0.0:22 0.0.0.0:*
LISTEN    0 128 127.0.0.1:6010 0.0.0.0:*
LISTEN    0 128 0.0.0.0:40667 0.0.0.0:*
LISTEN    0 64 0.0.0.0:2049 0.0.0.0:*
LISTEN    0 128 [::]:46347 [::]:*
LISTEN    0 128 [::]:111 [::]:*
LISTEN    0 128 [::]:20048 [::]:*
LISTEN    0 64 [::]:38739 [::]:*
LISTEN    0 128 [::]:22 [::]:*
LISTEN    0 128 [::1]:6010 [::]:*
LISTEN    0 64 [::]:2049  [::]:*


/etc/exports is presently -
[root@ASRock-J3455M bobg]# cat /etc/exports
/exports/home    
192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check,fsid=0)


This was working until the power interruption about 24 hours ago.A 
second computer on the same LAN also fails to connect to this server ...


Perhaps a reboot will help? I'll try that next ...

Bob

--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10  FEDORA-27/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/QRDXRCVWENKU2754RQMUTJIMTGGYJRRS/


Re: lost nfs mount -

2018-07-19 Thread Tom Horsley
On Fri, 20 Jul 2018 07:44:14 +0800
Ed Greshko wrote:

> Well, there is your problem.   You need to check your /etc/exports file.

Yea, it is insanely picky about exports. If you mention a
system name it can't resolve, it refuses to do anything instead
of just ignoring the one system. Several times at work someone has
cleaned old system names out of the DNS server and suddenly
NFS stops working on some machines till you find the old name
in an old exports file and clean it up there as well.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/MASU3VVMJ5RBCM24Q2JTSOWMAZWJ5DRO/


Re: lost nfs mount -

2018-07-19 Thread Ed Greshko
On 07/20/18 07:36, Bob Goodwin wrote:
> .
> [root@ASRock-J3455M bobg]# systemctl status nfs
> ● nfs-server.service - NFS server and services
>    Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor
> preset: disabled)
>   Drop-In: /run/systemd/generator/nfs-server.service.d
>    └─order-with-mounts.conf
>    Active: failed (Result: exit-code) since Thu 2018-07-19 19:31:12 EDT; 24s 
> ago
>   Process: 1476 ExecStopPost=/usr/sbin/exportfs -f (code=exited, 
> status=0/SUCCESS)
>   Process: 1475 ExecStopPost=/usr/sbin/exportfs -au (code=exited, 
> status=0/SUCCESS)
>   Process: 1474 ExecStartPre=/usr/sbin/exportfs -r (code=exited, 
> status=1/FAILURE)
>
> Jul 19 19:31:12 ASRock-J3455M systemd[1]: Starting NFS server and services...
> Jul 19 19:31:12 ASRock-J3455M exportfs[1474]: exportfs: Failed to stat
> /mnt/test/backups: No such file or director

Well, there is your problem.   You need to check your /etc/exports file.

For example  If I make an error in my exports file and type "hom" instead of
"home" I get

● nfs-server.service - NFS server and services
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor
preset: disabled)
  Drop-In: /run/systemd/generator/nfs-server.service.d
   └─order-with-mounts.conf
   Active: failed (Result: exit-code) since Fri 2018-07-20 07:40:22 CST; 2min 
57s ago
  Process: 7259 ExecStopPost=/usr/sbin/exportfs -f (code=exited, 
status=0/SUCCESS)
  Process: 7258 ExecStopPost=/usr/sbin/exportfs -au (code=exited, 
status=0/SUCCESS)
  Process: 7233 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS)
  Process: 4800 ExecStart=/bin/sh -c if systemctl -q is-active gssproxy; then
systemctl restart gssproxy ; fi (code=exited, status=0/SUCCESS)
  Process: 4787 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, 
status=0/SUCCESS)
  Process: 7257 ExecStartPre=/usr/sbin/exportfs -r (code=exited, 
status=1/FAILURE)
 Main PID: 4800 (code=exited, status=0/SUCCESS)

Jul 20 07:40:22 f28k-b1.greshko.com systemd[1]: Starting NFS server and 
services...
Jul 20 07:40:22 f28k-b1.greshko.com exportfs[7257]: exportfs: Failed to stat
/hom/egreshko: No such file or directory
Jul 20 07:40:22 f28k-b1.greshko.com systemd[1]: nfs-server.service: Control 
process
exited, code=exited status=1
Jul 20 07:40:22 f28k-b1.greshko.com systemd[1]: nfs-server.service: Failed with
result 'exit-code'.
Jul 20 07:40:22 f28k-b1.greshko.com systemd[1]: Stopped NFS server and services.


-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/YNY3NKNDZDEVDHVE745VXBQC3YLJK2LH/


Re: lost nfs mount -

2018-07-19 Thread Bob Goodwin

On 07/19/18 18:25, Ed Greshko wrote:

On 07/20/18 05:58, Bob Goodwin wrote:

On 07/19/18 17:42, Ed Greshko wrote:

The server is a Fedora system, yes?  And, has it been rebooted?

.
Fedora 27 and 28, rebooted several times today ...

I probably should have mentioned doing:

[root@Box10 86data]# ss -t -l -n
State Recv-Q Send-Q  Local
Address:Port  Peer Address:Port
LISTEN    0  128
0.0.0.0:60705  0.0.0.0:*
LISTEN    0  128
0.0.0.0:111    0.0.0.0:*
LISTEN    0  32
192.168.124.1:53 0.0.0.0:*
LISTEN    0  128
0.0.0.0:22 0.0.0.0:*
LISTEN    0  5
0.0.0.0:631    0.0.0.0:*
LISTEN    0  128
[::]:59745 [::]:*
LISTEN    0  128
[::]:111   [::]:*
LISTEN    0  128
[::]:22    [::]:*
LISTEN    0  5
[::]:631   [::]:*

I don't currently have a Fedora system running as a NFSv4 server...but what do 
you
get when you do this from a client?

telnet yourserver 2049

.
[root@Box10 86data]# telnet 192.168.1.86 2049
Trying 192.168.1.86...
telnet: connect to address 192.168.1.86: Connection refused



That means the nfs server isn't running

I have a Fedora server now up on my end running F28

Do you have something like this?

[root@f28k-b1 ~]# systemctl status nfs
● nfs-server.service - NFS server and services
    Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor 
pre>
   Drop-In: /run/systemd/generator/nfs-server.service.d
    └─order-with-mounts.conf
    Active: active (exited) since Fri 2018-07-20 06:10:15 CST; 13min ago
   Process: 4800 ExecStart=/bin/sh -c if systemctl -q is-active gssproxy; then 
syst>
   Process: 4787 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, 
status=0/S>
   Process: 4786 ExecStartPre=/usr/sbin/exportfs -r (code=exited, 
status=0/SUCCESS)
  Main PID: 4800 (code=exited, status=0/SUCCESS)

Jul 20 06:10:15 f28k-b1.greshko.com systemd[1]: Starting NFS server and 
services...
Jul 20 06:10:15 f28k-b1.greshko.com systemd[1]: Started NFS server and services.



.
[root@ASRock-J3455M bobg]# systemctl status nfs
● nfs-server.service - NFS server and services
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; 
vendor preset: disabled)

  Drop-In: /run/systemd/generator/nfs-server.service.d
   └─order-with-mounts.conf
   Active: failed (Result: exit-code) since Thu 2018-07-19 19:31:12 
EDT; 24s ago
  Process: 1476 ExecStopPost=/usr/sbin/exportfs -f (code=exited, 
status=0/SUCCESS)
  Process: 1475 ExecStopPost=/usr/sbin/exportfs -au (code=exited, 
status=0/SUCCESS)
  Process: 1474 ExecStartPre=/usr/sbin/exportfs -r (code=exited, 
status=1/FAILURE)


Jul 19 19:31:12 ASRock-J3455M systemd[1]: Starting NFS server and 
services...
Jul 19 19:31:12 ASRock-J3455M exportfs[1474]: exportfs: Failed to stat 
/mnt/test/backups: No such file or director
Jul 19 19:31:12 ASRock-J3455M systemd[1]: nfs-server.service: Control 
process exited, code=exited status=1

Jul 19 19:31:12 ASRock-J3455M systemd[1]: Stopped NFS server and services.
Jul 19 19:31:12 ASRock-J3455M systemd[1]: nfs-server.service: Unit 
entered failed state.
Jul 19 19:31:12 ASRock-J3455M systemd[1]: nfs-server.service: Failed 
with result 'exit-code'.



--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10  FEDORA-27/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/ZGZMWMVIEEHEHI2C323ITIIE3MG4KN56/


Re: lost nfs mount -

2018-07-19 Thread Tom Horsley
On Thu, 19 Jul 2018 17:16:46 -0400
Bob Goodwin wrote:

> I have all the usual connections through my LAN but can not mount the 
> NFS4 server

I've sometimes had individual systems get into some strange
state where an NFS server doesn't like them (but is fine with
other systems). Short of a reboot sometimes just restarting
NFS on the server works. (Though I'm never sure which one
of the dozens of NFS related services is the one I need
to restart :-).
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/QS6DN6444JAITIHHNY5AFT2VI6VOK7PN/


Re: lost nfs mount -

2018-07-19 Thread Ed Greshko
On 07/20/18 05:58, Bob Goodwin wrote:
> On 07/19/18 17:42, Ed Greshko wrote:
>> The server is a Fedora system, yes?  And, has it been rebooted?
> .
> Fedora 27 and 28, rebooted several times today ...
>
> I probably should have mentioned doing:
>
> [root@Box10 86data]# ss -t -l -n
> State Recv-Q Send-Q  Local
> Address:Port  Peer Address:Port   
> LISTEN    0  128  
> 0.0.0.0:60705  0.0.0.0:*  
> LISTEN    0  128  
> 0.0.0.0:111    0.0.0.0:*  
> LISTEN    0  32 
> 192.168.124.1:53 0.0.0.0:*  
> LISTEN    0  128  
> 0.0.0.0:22 0.0.0.0:*  
> LISTEN    0  5
> 0.0.0.0:631    0.0.0.0:*  
> LISTEN    0  128 
> [::]:59745 [::]:*  
> LISTEN    0  128 
> [::]:111   [::]:*  
> LISTEN    0  128 
> [::]:22    [::]:*  
> LISTEN    0  5   
> [::]:631   [::]:*   
>> I don't currently have a Fedora system running as a NFSv4 server...but what 
>> do you
>> get when you do this from a client?
>>
>> telnet yourserver 2049
> .
> [root@Box10 86data]# telnet 192.168.1.86 2049
> Trying 192.168.1.86...
> telnet: connect to address 192.168.1.86: Connection refused
>
>

That means the nfs server isn't running

I have a Fedora server now up on my end running F28

Do you have something like this?

[root@f28k-b1 ~]# systemctl status nfs
● nfs-server.service - NFS server and services
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor 
pre>
  Drop-In: /run/systemd/generator/nfs-server.service.d
   └─order-with-mounts.conf
   Active: active (exited) since Fri 2018-07-20 06:10:15 CST; 13min ago
  Process: 4800 ExecStart=/bin/sh -c if systemctl -q is-active gssproxy; then 
syst>
  Process: 4787 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, 
status=0/S>
  Process: 4786 ExecStartPre=/usr/sbin/exportfs -r (code=exited, 
status=0/SUCCESS)
 Main PID: 4800 (code=exited, status=0/SUCCESS)

Jul 20 06:10:15 f28k-b1.greshko.com systemd[1]: Starting NFS server and 
services...
Jul 20 06:10:15 f28k-b1.greshko.com systemd[1]: Started NFS server and services.


-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.


signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/C5XRMNLKR2YS2KR7DPMEJFMQ4QTDCAZF/


Re: lost nfs mount -

2018-07-19 Thread Ed Greshko
On 07/20/18 05:16, Bob Goodwin wrote:
> I had a power interruption this morning, everything is on UPS's but we are 
> raising
> a new puppy who gets into everythingit seems.
>
> I have all the usual connections through my LAN but can not mount the NFS4 
> server, 
> /can ssh and sftp to it. //I/'ve tried what I can think of, it doesn't seem 
> to be a
> firewall or selinux problem. it has worked well until the power failure. I 
> think
> something is corrupted in the server ... I have a similar server running Samba
> which connects and runs as usual.
>
> I could use some suggestions of where to look next.

The server is a Fedora system, yes?  And, has it been rebooted?

I don't currently have a Fedora system running as a NFSv4 server...but what do 
you
get when you do this from a client?

telnet yourserver 2049


-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/QBLLKLWYWP6CJGS4RSAPF2FAVAPN6DDB/


lost nfs mount -

2018-07-19 Thread Bob Goodwin
I had a power interruption this morning, everything is on UPS's but we 
are raising a new puppy who gets into everythingit seems.


I have all the usual connections through my LAN but can not mount the 
NFS4 server, /can ssh and sftp to it. //I/'ve tried what I can think of, 
it doesn't seem to be a firewall or selinux problem. it has worked well 
until the power failure. I think something is corrupted in the server 
... I have a similar server running Samba which connects and runs as usual.


I could use some suggestions of where to look next.

Bob

--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10  FEDORA-27/64bit LINUX XFCE Fastmail POP3

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/H7MBRVTDVPPG4T3LYA2AHQNQUCHSILII/