01-23-2018
Can you share logs regrading the sentence 'Solaris gets confused' ?
Something must be written in logs, feel free to paste them here if possible.
As for Linux zfs i have no experience, but the common denominator zpool and zfs version should be able to coexist across various systems if configured properly.
Since you are able to use the filesystem on both operating system, we shall assume it is.
Lets say you have a situation :
/home/user -> this is a regular part of rpool on solaris
/home/user -> this is a regular part of root volume group on linux
A third disk is introduced and zpool is created in <input operating system on which you have created the zpool>.
For the sake of argument the mountpoint for that zpool is mounted on /personal_files and it has directory structure behind (Documents, vbox etc.)
The mountpoint is the same on both operating systems.
A soft link is created in linux /home/user pointing to /personal_files/Documents
A soft link is created in Solaris /home/user pointing to /personal_files/Documents
Is the above correct ?
In that case, one should not have any issues regarding mounting the home directory, regardless of soft links pointing to data disk.
No ?
Please provide the exact layout and configuration details as possible.
Including commands used for creation of zpool (operating system where it was initially created and version and zfs properties).
Regards
Peasant.
9 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
until recently I've been using the following command successfully:
mount -t smbfs -o username=my_user_name,password=password /home/temp/ //oldserver/openexchange
To connect to a Win2000 shared folder called openexchange on a machine called //oldserver.
But as from today, I've been getting... (2 Replies)
Discussion started by: cw1972
2 Replies
2. SCO
Dear sir,
In my SCO unix system while running an isql because of the size of the files created the ./data directory become full and now I cannot boot the system in normal mode. I am botting the machine in single user mode but i cannot delete the files from /data directory cos it is not... (2 Replies)
Discussion started by: khelen
2 Replies
3. UNIX for Dummies Questions & Answers
Hi
what is the difference between the directory named /home and the user's home directory?
can anyone plz reply?
really confuse about it!!!!!!!!
thank you (1 Reply)
Discussion started by: nokia3100
1 Replies
4. Slackware
hi
I installed slackware.
How can I mount new partition
I edit etc/fstab and add new mount point("back")
What should I do next?
When I perfom:
mount /back
it doesnt work. (16 Replies)
Discussion started by: tjay83
16 Replies
5. SuSE
Our home directory is not mounting in SUSE 10, can you please help me in this regard.
Thanks (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
6. Solaris
Hi,
I've created solaris user which has both FTP and SFTP Access. Using the "ftpaccess" configuration file options "guest-root" and "restricted-uid", i can restrict the user to a specific directory. But I'm unable to restrict the user when the user is logged in using SFTP.
The aim is to... (1 Reply)
Discussion started by: sftpuser
1 Replies
7. UNIX for Advanced & Expert Users
Hi,
I would like to know how can we mount a directory using nfs v4 ?
When I use the below command, I am not sure what nfs version am using to mount the directory.
mount -t <server_name>:<shared_directory> <shared_directory>.
eg:
mount -t 10.50.0.8:/home/arun/mount/share_dir... (7 Replies)
Discussion started by: arunsriniv
7 Replies
8. AIX
Hi All,
Recently I came to know my / root file system is getting full because of application directory /siebel/
I have one option.
1) Down the application , take full backup
2)change the filesystem ownership
2)copy the contents into that filesystem
cp -pr /siebel/* /siebelfs/*
3)Inform... (9 Replies)
Discussion started by: Thala
9 Replies
9. Solaris
Hello,
I've just started using a Solaris machine with SunOS 5.10.
After the machine is turned on, I open a Console window and at the prompt, if I execute a pwd command, it tells me I'm at my home directory (someone configured "myuser" as default user after init).
... (2 Replies)
Discussion started by: egyassun
2 Replies
LEARN ABOUT FREEBSD
gptzfsboot
GPTZFSBOOT(8) BSD System Manager's Manual GPTZFSBOOT(8)
NAME
gptzfsboot -- GPT bootcode for ZFS on BIOS-based computers
DESCRIPTION
gptzfsboot is used on BIOS-based computers to boot from a filesystem in a ZFS pool. gptzfsboot is installed in a freebsd-boot partition of a
GPT-partitioned disk with gpart(8).
IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptzfsboot only boots from tables with 128 partitions or less.
BOOTING
gptzfsboot tries to find all ZFS pools that are composed of BIOS-visible hard disks or partitions on them. gptzfsboot looks for ZFS device
labels on all visible disks and in discovered supported partitions for all supported partition scheme types. The search starts with the disk
from which gptzfsboot itself was loaded. Other disks are probed in BIOS defined order. After a disk is probed and gptzfsboot determines
that the whole disk is not a ZFS pool member, the individual partitions are probed in their partition table order. Currently GPT and MBR
partition schemes are supported. With the GPT scheme, only partitions of type freebsd-zfs are probed. The first pool seen during probing is
used as a default boot pool.
The filesystem specified by the bootfs property of the pool is used as a default boot filesystem. If the bootfs property is not set, then
the root filesystem of the pool is used as the default. zfsloader(8) is loaded from the boot filesystem. If /boot.config or /boot/config is
present in the boot filesystem, boot options are read from it in the same way as boot(8).
The ZFS GUIDs of the first successfully probed device and the first detected pool are made available to zfsloader(8) in the
vfs.zfs.boot.primary_vdev and vfs.zfs.boot.primary_pool variables.
USAGE
Normally gptzfsboot will boot in fully automatic mode. However, like boot(8), it is possible to interrupt the automatic boot process and
interact with gptzfsboot through a prompt. gptzfsboot accepts all the options that boot(8) supports.
The filesystem specification and the path to zfsloader(8) are different from boot(8). The format is
[zfs:pool/filesystem:][/path/to/loader]
Both the filesystem and the path can be specified. If only a path is specified, then the default filesystem is used. If only a pool and
filesystem are specified, then /boot/zfsloader is used as a path.
Additionally, the status command can be used to query information about discovered pools. The output format is similar to that of zpool
status (see zpool(8)).
The configured or automatically determined ZFS boot filesystem is stored in the zfsloader(8) loaddev variable, and also set as the initial
value of the currdev variable.
FILES
/boot/gptzfsboot boot code binary
/boot.config parameters for the boot block (optional)
/boot/config alternative parameters for the boot block (optional)
EXAMPLES
gptzfsboot is typically installed in combination with a ``protective MBR'' (see gpart(8)). To install gptzfsboot on the ada0 drive:
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0
gptzfsboot can also be installed without the PMBR:
gpart bootcode -p /boot/gptzfsboot -i 1 ada0
SEE ALSO
boot.config(5), boot(8), gpart(8), loader(8), zfsloader(8), zpool(8)
HISTORY
gptzfsboot appeared in FreeBSD 7.3.
AUTHORS
This manual page was written by Andriy Gapon <avg@FreeBSD.org>.
BUGS
gptzfsboot looks for ZFS meta-data only in MBR partitions (known on FreeBSD as slices). It does not look into BSD disklabel(8) partitions
that are traditionally called partitions. If a disklabel partition happens to be placed so that ZFS meta-data can be found at the fixed off-
sets relative to a slice, then gptzfsboot will recognize the partition as a part of a ZFS pool, but this is not guaranteed to happen.
BSD
September 15, 2014 BSD