Performing sfspartition does not preserve file timestamps across device (partition) boundaries (Doc ID 2869496.1)

Last updated on AUGUST 19, 2022

Applies to:

Symptoms

While running sfspartition from source to target partition with different mounts does break the file timestamps.

Source NFS mount: /fs_backup

Target NFS mount: /fs0,/fs1,/fs2,/fs3,/fs4,/fs5,/fs6,/fs7,/fs8,/fs9

Moving files using mv command from /fs_backup/att to /fs0/att will preserve the file timestamp.

Whereas using the sfspartition utility will move the files to the new partitions and change the file timestamp to the current execution time of the utility.

 To replicate the issue perform the following step:

1. Copy the structure of /refresh/siebel/fs into a different partition (/tmp in the above example).

[siebel@linux bin]$ df -kh

Filesystem Size Used Avail Use% Mounted on

/dev/sda6 2.9G 18M 2.8G 1% /tmp

/dev/sda2 63G 45G 15G 76% /refresh

2. Add attachement into Siebel application and check their timestamp.

3. Run sfspartion.

cd /siebel/ses/siebsrvr

. ./siebenv.sh

cd /siebel/ses/siebsrvr/bin

sfspartition /O /refresh/siebel/fs /F /tmp/fs /H Y

4. Check the timestamp after the attachments were moved to /tmp/fs.

The errors can also be seen running sfspartition with truss command:

execve("/siebapp/siebel/ses/siebsrvr/bin/sfspartition", 0xFFBFEF7C, 0xFFBFEF9C) argc = 7

sysinfo(SI_MACHINE, "sun4v", 257) = 6

mmap(0x00000000, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFF1D4000

...

renameat(AT_FDCWD, "/fs_backup/att_sami/S_XMLP_REPOUTPT_1-IXPCISE_1-CUT2ZUN.SAF", AT_FDCWD, "/fs1/att/S_XMLP_REPOUTPT_1-IXPCISE_1-CUT2ZUN.SAF") Err#18 EXDEV

This is happening because of "EXDEV: cross-device link not permitted" error seen in truss: EXDEV oldpath and newpath are not on the same mounted filesystem.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.