xfs_reno
Hi Dave,
I tried to gather Barrys SOB, but failed so far. His trace ends in 2009 google wise.
How is this case usually handled?
Here's the current state of things.
Cheers,
Pete
---------- Weitergeleitete Nachricht ----------
Betreff: xfs_reno
Datum: Mittwoch, 6. März 2013, 12:52:19
Von: Hans-Peter Jansen <[email protected]>
An: [email protected]
Hi Barry,
attached is a slightly mangled version of your xfs_reno tool, that I badly needed recently. While at it, I plan to submit it, as it saved my *ss. Thanks.
Apart from relocation to xfsprogs, I just changed this
+ log_message(LOG_DEBUG, "%s: %llu %lu %s", msg, node->ino,
+ node->numpaths, node->paths[0]);
from %llu to %lu for the node->numpaths argument. It might still be wrong, as numpath is defined as nlink_t which is a __u32 type, but the %s printed garbage like this:
Scanning directory tree...xfs_reno: add_node_path: ino 8611163235, path /work/dlbase/hosts/11.2/pico/var/run/screensxfs_reno: add_node_path: ino 8611163233, path /work/dlbase/hosts/11.2/pico/var/run/pcscd/pcscd.eventsxfs_reno: add_node_path: ino 8611163234, path /work/dlbase/hosts/11.2/pico/var/run/uscreensxfs_reno: nodehash: 8611163233 692488159933497345 ��]��f�e�xfs_reno: nodehash: 8611163234 692366801337581569 ��]��f�e�xfs_reno: nodehash: 8611163235 692223830466232321 ��]��f�e�
I guess, gcc is smart enough to see, that the struct members overlap here, and prints the paths[0] argument as a %llu value. What do you think?
Anyway, I will revise this during the course of creating a xlstests test for xfs_reno...
Do you allow me to add your Signed-off-by to this patch?
If you want to build this, apply both patches to xfsprogs.
TIA,
Pete
-------------------------------------------------------------
From: "Barry Naujok" <bnaujok () sgi ! com> Date: 2007-10-04 4:25:16 Message-ID: op.tznnweh23jf8g2 () pc-bnaujok ! melbourne ! sgi ! com
The attached tool allows an inode64 filesystem to be converted to inode32. For this to work, the filesystem has to be mounted inode32 before it's run.
Second version including these changes:
- Major one is that symlinks are now supported, but only owner, group and extended attributes are copied for them (not times or inode attributes).
- Man page!
See: http://marc.info/?l=linux-xfs&m=119130906204596&w=2
http://marc.info/?l=linux-xfs&m=119147190705051&w=2
Relocated to xfsprogs and other minor adjustments by H.P. Jansen.
man/man8/xfs_reno.8 new file +117 -0
@@ -0,0 +1,117 @@ +.TH xfs_reno 8 +.SH NAME +xfs_reno \- renumber XFS inodes +.SH SYNOPSIS +.B xfs_reno +[ +.B \-fnpqv +] [ +.B \-P +.I interval +] +.I path +.br +.B xfs_reno \-r +.I recover_file +.SH DESCRIPTION +.B xfs_reno +is applicable only to XFS filesystems. +.PP +.B xfs_reno +renumbers inodes. XFS supports 64-bit inode numbers, although by +default it will avoid creating inodes with numbers greater than +what can be contained within a 32-bit number. If a filesystem does +contain inode numbers greater than 32-bits, then this can conflict with +applications that do not support them. +To recover from this situation previously, affected files would need +to be copied (and so get a new inode number) and the old version +removed. This can be time consuming and impractical for very large +files and filesystems. +.B xfs_reno +can be used to renumber such inodes quickly. +.B xfs_reno +will copy the inodes of affected files and move the data from the old +inode to the new without having to copy the data. +.B xfs_reno +relies on XFS in the kernel to allocate a new inode number, so if the +filesystem has been mounted with the +.I inode64 +mount option, the new inodes will quite possibly have inode numbers +greater than 32-bits. +.PP +.B xfs_reno +should only be used on a filesystem where it is necessary to +renumber inodes. Use of +.B xfs_reno +on a regular basis is +.IR "not recommended" . +Apart from application compatibility, there is no particular advantage +to be had from renumbering inodes. +.PP +.B xfs_reno +works by traversing a directory tree, scanning all the directories +and noting which files require renumbering. Once the scanning phase +is done, it will process the appropriate files and directories. The +directory's absolute pathname must be given to +.BR xfs_reno . +The following options are accepted by +.BR xfs_reno . +.TP +.B \-f +Force conversion on all inodes, rather than just those with a 64-bit +inode number. This is not particularly useful except for debugging +purposes. +.TP +.B \-n +Do nothing, perform a trial run. +.TP +.B \-v +Increases the verbosity of progress and error messages. Additional +.BR \-v 's +can be used to further increase verbosity. +.TP +.B \-q +Do not report progress, only errors. +.TP +.B \-p +Show progress status. +.TP +.BI \-P " seconds" +Set the interval for the progress status in seconds. The default is 1 +second. +.TP +.B \-r +Recover from an interrupted run. If +.B xfs_reno +is interrupted, it will leave a file called +.I xfs_reno.recover +in the directory specified on the command line. This file will +contain enough information so that +.B xfs_reno +can either finish processing the file it was working on when +interrupted or back out the last change it made, depending on how far +through the process it had progressed. +.B xfs_reno +will only recover the single file it was working on so it will need +to be run again on the directory to be sure that all the appropriate +inodes have been converted. +.SH EXAMPLES +To renumber inodes with 64-bit inode numbers: +.IP +.B # xfs_reno -p /path/to/directory +.PP +To recover from an interrupted run: +.IP +.B # xfs_reno -r /path/to/directory/xfs_reno.recover +.PP +.SH FILES +.PD +.TP +.I /path/xfs_reno.recover +records the state where renumbering was interrupted. +.PD +.SH SEE ALSO +.BR xfs_fsr (8), +.BR xfs_ncheck (8), +.BR fstab (5), +.BR xfs (5).
reno/Makefile new file +19 -0
@@ -0,0 +1,19 @@ +# +# Copyright (c) 2007 Silicon Graphics, Inc. All Rights Reserved. +# + +TOPDIR = .. +include $(TOPDIR)/include/builddefs + +LTCOMMAND = xfs_reno +CFILES = xfs_reno.c +LLDLIBS = $(LIBATTR) + +default: $(LTCOMMAND) + +include $(BUILDRULES) + +install: default + $(INSTALL) -m 755 -d $(PKG_SBIN_DIR) + $(LTINSTALL) -m 755 $(LTCOMMAND) $(PKG_SBIN_DIR) +install-dev:
reno/xfs_reno.c new file +2040 -0
2,040 lines not on this page · raw message
Makefile +1 -1
@@ -41,7 +41,7 @@ endif LIB_SUBDIRS = libxfs libxlog libxcmd libhandle libdisk TOOL_SUBDIRS = copy db estimate fsck fsr growfs io logprint mkfs quota \ - mdrestore repair rtcp m4 man doc po debian + mdrestore repair reno rtcp m4 man doc po debian SUBDIRS = include $(LIB_SUBDIRS) $(TOOL_SUBDIRS)
Add the necessary autoconf magic in order to be able to compile anything dependent from libattr, e.g. xfs_reno.
Shamelessly stolen from xfsdump.
Thanks to Dave Chinner for advice.
configure.ac +4 -0
@@ -101,6 +101,10 @@ AC_PACKAGE_NEED_UUIDCOMPARE AC_PACKAGE_NEED_PTHREAD_H AC_PACKAGE_NEED_PTHREADMUTEXINIT +AC_PACKAGE_NEED_ATTRIBUTES_H +AC_PACKAGE_NEED_ATTRIBUTES_MACROS +AC_PACKAGE_NEED_ATTRGET_LIBATTR + AC_HAVE_FADVISE AC_HAVE_MADVISE AC_HAVE_MINCORE
include/builddefs.in +1 -0
@@ -34,6 +34,7 @@ LIBTERMCAP = @libtermcap@ LIBEDITLINE = @libeditline@ LIBREADLINE = @libreadline@ LIBBLKID = @libblkid@ +LIBATTR = @libattr@ LIBXFS = $(TOPDIR)/libxfs/libxfs.la LIBXCMD = $(TOPDIR)/libxcmd/libxcmd.la LIBXLOG = $(TOPDIR)/libxlog/libxlog.la
m4/package_attrdev.m4 new file +79 -0
79 lines not on this page · raw message
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 4 lines · Hans-Peter Jansen
Hi Dave,
I tried to gather Barrys SOB, but failed so far. His trace ends in 2009 google wise.
I've got him. ;) I asked him to chime in here or maybe email you personally.
Thanks,
-Eric
Quoted 53 lines
How is this case usually handled?
Here's the current state of things.
Cheers,
Pete---------- Weitergeleitete Nachricht ----------
Betreff:
xfs_reno
Datum: Mittwoch, 6. März 2013, 12:52:19
Von: Hans-Peter Jansen <[email protected]>
An: [email protected]Hi Barry,
attached is a slightly mangled version of your
xfs_renotool, that I badly needed recently. While at it, I plan to submit it, as it saved my *ss. Thanks.Apart from relocation to xfsprogs, I just changed this
reno/xfs_reno.c new file +2
-0+log_message (LOG_DEBUG ,"%s: %llu %lu %s" , msg, node->ino, + node->numpaths, node->paths[0 ]);from %llu to %lu for the
node->numpathsargument. It might still be wrong, as numpath is defined asnlink_twhich is a__u32type, but the %s printed garbage like this:Scanning directory tree...
xfs_reno:add_node_path: ino 8611163235, path /work/dlbase/hosts/11.2/pico/var/run/screensxfs_reno:add_node_path: ino 8611163233, path /work/dlbase/hosts/11.2/pico/var/run/pcscd/pcscd.eventsxfs_reno:add_node_path: ino 8611163234, path /work/dlbase/hosts/11.2/pico/var/run/uscreensxfs_reno: nodehash: 8611163233 692488159933497345 ��]��f�e�xfs_reno: nodehash: 8611163234 692366801337581569 ��]��f�e�xfs_reno: nodehash: 8611163235 692223830466232321 ��]��f�e�I guess, gcc is smart enough to see, that the struct members overlap here, and prints the paths[0] argument as a %llu value. What do you think?
Anyway, I will revise this during the course of creating a xlstests test for
xfs_reno...Do you allow me to add your Signed-off-by to this patch?
If you want to build this, apply both patches to xfsprogs.
TIA,
Pete
Quoted 9 lines
-------------------------------------------------------------
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 8 lines · Hans-Peter Jansen
Hi Dave,
I tried to gather Barrys SOB, but failed so far. His trace ends in 2009 google wise.
How is this case usually handled?
Here's the current state of things.
He was working for SGI at the time, so you should be able to get anyone from SGI provide a valid S-O-B if needed.
As it is, I can probably verify the patch origins sufficiently to add a SOB to it as:
http://oss.sgi.com/archives/xfs/2007-11/msg00769.html
It's pretty clear that the code was released under the GPL and free from any tainted code by SGI. The post I'm pointing to above is one I made while an SGI employee, and it effectively verifies the origin of the code in the same way a S-O-B does.
So, you probably don't even need to chase a S-O-B from SGI if you just point at that email and attribute the code correctly. i.e. retaining al the SGI copyright notices in the code and saying inteh patch description that the code was originally authored by SGI and released under the same license as the rest of the xfs userspace code.
Cheers,
Dave.
Signature · 7 lines
Dave Chinner [email protected] _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Hi Pete,
Quoted 23 lines · Dave Chinner
Quoted 8 lines · Hans-Peter Jansen
Hi Dave,
I tried to gather Barrys SOB, but failed so far. His trace ends in 2009 google wise.
How is this case usually handled?
Here's the current state of things.
He was working for SGI at the time, so you should be able to get anyone from SGI provide a valid S-O-B if needed.
As it is, I can probably verify the patch origins sufficiently to add a SOB to it as:
http://oss.sgi.com/archives/xfs/2007-11/msg00769.html
It's pretty clear that the code was released under the GPL and free from any tainted code by SGI. The post I'm pointing to above is one I made while an SGI employee, and it effectively verifies the origin of the code in the same way a S-O-B does.
Quoted 6 lines
So, you probably don't even need to chase a S-O-B from SGI if you just point at that email and attribute the code correctly. i.e. retaining al the SGI copyright notices in the code and saying inteh patch description that the code was originally authored by SGI and released under the same license as the rest of the xfs userspace code.
Looks good to me as is. Links and attribution are in the header, copyright notices, etc. We'll clean up that copyright header in the Makefile with a separate commit authored by a current SGI employee.
You can add a Signed-off-by: Ben Myers <[email protected]> if you want. No need to repost just for that.
Thanks for spending the time!
Regards,
Ben
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 51 lines · Hans-Peter Jansen
Hi Dave,
I tried to gather Barrys SOB, but failed so far. His trace ends in 2009 google wise.
How is this case usually handled?
Here's the current state of things.
Cheers,
Pete---------- Weitergeleitete Nachricht ----------
Betreff:
xfs_reno
Datum: Mittwoch, 6. März 2013, 12:52:19
Von: Hans-Peter Jansen<[email protected]>
An: [email protected]Hi Barry,
attached is a slightly mangled version of your
xfs_renotool, that I badly needed recently. While at it, I plan to submit it, as it saved my *ss. Thanks.Apart from relocation to xfsprogs, I just changed this
reno/xfs_reno.c new file +2
-0+log_message (LOG_DEBUG ,"%s: %llu %lu %s" , msg, node->ino, + node->numpaths, node->paths[0 ]);from %llu to %lu for the
node->numpathsargument. It might still be wrong, as numpath is defined asnlink_twhich is a__u32type, but the %s printed garbage like this:Scanning directory tree...
xfs_reno:add_node_path: ino 8611163235, path /work/dlbase/hosts/11.2/pico/var/run/screensxfs_reno:add_node_path: ino 8611163233, path /work/dlbase/hosts/11.2/pico/var/run/pcscd/pcscd.eventsxfs_reno:add_node_path: ino 8611163234, path /work/dlbase/hosts/11.2/pico/var/run/uscreensxfs_reno: nodehash: 8611163233 692488159933497345 ��]��f�e�xfs_reno: nodehash: 8611163234 692366801337581569 ��]��f�e�xfs_reno: nodehash: 8611163235 692223830466232321 ��]��f�e�I guess, gcc is smart enough to see, that the struct members overlap here, and prints the paths[0] argument as a %llu value. What do you think?
Anyway, I will revise this during the course of creating a xlstests test for
xfs_reno...
Quoted 7 lines
Do you allow me to add your Signed-off-by to this patch?
If you want to build this, apply both patches to xfsprogs.
TIA,
Pete
Have you been getting "Out of memory" warnings on your runs? I am.
Compiling, I get the warnings about having "\r" in the strings. For example:
reno/xfs_reno.c:1415: internationalized messages should not contain the `\r' escape sequence
----------
I wonder if we should add a temp directory option. It seems to want to use the parent directory of the directory as a temporary. Below is the result of running xfs_reno on the target directory is "/mnt/xxx (changing the \r to <^M>\n for the email):
xfs_reno: directory: 128 1 /mn<^M>xfs_reno: /mnt/xfs_reno_epdaJc: Cannet set target extended attributes<^M>xfs_reno: failed to rename: '/mnt/xxx/origin' to '/mnt/xfs_reno_NXQLWI/origin' <^M>xfs_reno: unable to move directory contents: /mnt/xxx to /mnt/xfs_reno_NXQLWI <^M>xfs_reno: Cannot stat /mnt/xfs_reno_epdaJc: Inappropriate ioctl for device
<^M>xfs_reno: unable to duplicate directory attributes: /mnt/xfs_reno_epdaJc t/xxx
------
/mnt is not an XFS filesystem. When mounting on the root, say /mnt, the message look like:
xfs_reno: Cannot stat //xfs_reno_epdaJc: Inappropriate ioctl for device
Thank-you,
--Mark Tinguely.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Am Montag, 11. März 2013, 16:48:03 schrieb Mark Tinguely:
Quoted 53 lines · Hans-Peter Jansen
Quoted 52 lines
Hi Dave,
I tried to gather Barrys SOB, but failed so far. His trace ends in 2009 google wise.
How is this case usually handled?
Here's the current state of things.
Cheers,
Pete---------- Weitergeleitete Nachricht ----------
Betreff:
xfs_reno
Datum: Mittwoch, 6. März 2013, 12:52:19
Von: Hans-Peter Jansen<[email protected]>
An: [email protected]Hi Barry,
attached is a slightly mangled version of your
xfs_renotool, that I badly needed recently. While at it, I plan to submit it, as it saved my *ss. Thanks.Apart from relocation to xfsprogs, I just changed this
reno/xfs_reno.c new file +2
-0+log_message (LOG_DEBUG ,"%s: %llu %lu %s" , msg, node->ino, + node->numpaths, node->paths[0 ]);from %llu to %lu for the
node->numpathsargument. It might still be wrong, as numpath is defined asnlink_twhich is a__u32type, but the %s printed garbage like this:Scanning directory tree...
xfs_reno:add_node_path: ino 8611163235, path /work/dlbase/hosts/11.2/pico/var/run/screensxfs_reno:add_node_path: ino 8611163233, path /work/dlbase/hosts/11.2/pico/var/run/pcscd/pcscd.eventsxfs_reno:add_node_path: ino 8611163234, path /work/dlbase/hosts/11.2/pico/var/run/uscreensxfs_reno: nodehash: 8611163233 692488159933497345 ��]��f�e�xfs_reno: nodehash: 8611163234 692366801337581569 ��]��f�e�xfs_reno: nodehash: 8611163235 692223830466232321 ��]��f�e�I guess, gcc is smart enough to see, that the struct members overlap here, and prints the paths[0] argument as a %llu value. What do you think?
Anyway, I will revise this during the course of creating a xlstests test for
xfs_reno...
Quoted 8 lines
Quoted 6 lines
Do you allow me to add your Signed-off-by to this patch?
If you want to build this, apply both patches to xfsprogs.
TIA,
PeteHave you been getting "Out of memory" warnings on your runs? I am.
No, I would have mentioned them. But I guess, my file systems are tiny compared to yours. The affected FS have 2.8T and 4.1T, with former with many small files and directories, the latter with many 2G files.
Quoted 4 lines
Compiling, I get the warnings about having "\r" in the strings. For example:
reno/xfs_reno.c:1415: internationalized messages should not contain the `\r' escape sequence
Well, that's for the spin wheel, that might have interesting effects, when localized to right-to-left languages...
Quoted 3 lines
----------I wonder if we should add a temp directory option. It seems to want to use the parent directory of the directory as a temporary.
Without digging into this, I can only guess, but the whole point of xfs_reno is relocating the inodes on the FS in question *without* copying files around. Using a separate TEMP defeats this purpose, don't it?
It might be in order to add a note to the man page to not try to use it in "cross mount operation" scenarios.
Quoted 14 lines
Below is the
result of runningxfs_renoon the target directory is "/mnt/xxx(changing the \r to <^M>\n for the email):
xfs_reno: directory: 128 1 /mn<^M>xfs_reno:/mnt/xfs_reno_epdaJc: Cannet set target extended attributes<^M>xfs_reno: failed to rename: '/mnt/xxx/origin' to '/mnt/xfs_reno_NXQLWI/origin'
<^M>xfs_reno: unable to move directory contents:/mnt/xxxto/mnt/xfs_reno_NXQLWI
<^M>xfs_reno: Cannot stat/mnt/xfs_reno_epdaJc: Inappropriate ioctl for device
Quoted 8 lines
<^M>
xfs_reno: unable to duplicate directory attributes:/mnt/xfs_reno_epdaJct/xxx------/mnt is not an XFS filesystem. When mounting on the root, say /mnt, the message look like:
xfs_reno: Cannot stat //xfs_reno_epdaJc: Inappropriate ioctl for device
You lost me here. What I can say, is that using eg. "xfs_reno -vpn /work", hence on the mount point directly, did as advertised.
Cheers,
Pete
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 107 lines · Hans-Peter Jansen
Am Montag, 11. März 2013, 16:48:03 schrieb Mark Tinguely:
Quoted 53 lines · Hans-Peter Jansen
Quoted 52 lines
Hi Dave,
I tried to gather Barrys SOB, but failed so far. His trace ends in 2009 google wise.
How is this case usually handled?
Here's the current state of things.
Cheers,
Pete---------- Weitergeleitete Nachricht ----------
Betreff:
xfs_reno
Datum: Mittwoch, 6. März 2013, 12:52:19
Von: Hans-Peter Jansen<[email protected]>
An: [email protected]Hi Barry,
attached is a slightly mangled version of your
xfs_renotool, that I badly needed recently. While at it, I plan to submit it, as it saved my *ss. Thanks.Apart from relocation to xfsprogs, I just changed this
reno/xfs_reno.c new file +2
-0+log_message (LOG_DEBUG ,"%s: %llu %lu %s" , msg, node->ino, + node->numpaths, node->paths[0 ]);from %llu to %lu for the
node->numpathsargument. It might still be wrong, as numpath is defined asnlink_twhich is a__u32type, but the %s printed garbage like this:Scanning directory tree...
xfs_reno:add_node_path: ino 8611163235, path /work/dlbase/hosts/11.2/pico/var/run/screensxfs_reno:add_node_path: ino 8611163233, path /work/dlbase/hosts/11.2/pico/var/run/pcscd/pcscd.eventsxfs_reno:add_node_path: ino 8611163234, path /work/dlbase/hosts/11.2/pico/var/run/uscreensxfs_reno: nodehash: 8611163233 692488159933497345 ��]��f�e�xfs_reno: nodehash: 8611163234 692366801337581569 ��]��f�e�xfs_reno: nodehash: 8611163235 692223830466232321 ��]��f�e�I guess, gcc is smart enough to see, that the struct members overlap here, and prints the paths[0] argument as a %llu value. What do you think?
Anyway, I will revise this during the course of creating a xlstests test for
xfs_reno...Quoted 8 lines
Quoted 6 lines
Do you allow me to add your Signed-off-by to this patch?
If you want to build this, apply both patches to xfsprogs.
TIA,
PeteHave you been getting "Out of memory" warnings on your runs? I am.
No, I would have mentioned them. But I guess, my file systems are tiny compared to yours. The affected FS have 2.8T and 4.1T, with former with many small files and directories, the latter with many 2G files.
Quoted 4 lines
Compiling, I get the warnings about having "\r" in the strings. For example:
reno/xfs_reno.c:1415: internationalized messages should not contain the `\r' escape sequenceWell, that's for the spin wheel, that might have interesting effects, when localized to right-to-left languages...
Quoted 3 lines
----------I wonder if we should add a temp directory option. It seems to want to use the parent directory of the directory as a temporary.
Without digging into this, I can only guess, but the whole point of
xfs_renois relocating the inodes on the FS in question *without* copying files around. Using a separate TEMP defeats this purpose, don't it?It might be in order to add a note to the man page to not try to use it in "cross mount operation" scenarios.
Quoted 21 lines
Below is the
result of runningxfs_renoon the target directory is "/mnt/xxx(changing the \r to<^M>\n for the email):
xfs_reno: directory: 128 1 /mn<^M>xfs_reno:/mnt/xfs_reno_epdaJc: Cannet set target extended attributes<^M>xfs_reno: failed to rename: '/mnt/xxx/origin' to '/mnt/xfs_reno_NXQLWI/origin'
<^M>xfs_reno: unable to move directory contents:/mnt/xxxto/mnt/xfs_reno_NXQLWI
<^M>xfs_reno: Cannot stat/mnt/xfs_reno_epdaJc: Inappropriate ioctl for device<^M>
xfs_reno: unable to duplicate directory attributes:/mnt/xfs_reno_epdaJct/xxx------/mnt is not an XFS filesystem. When mounting on the root, say /mnt, the message look like:
Quoted 7 lines
Quoted 1 line
xfs_reno: Cannot stat //xfs_reno_epdaJc: Inappropriate ioctl for deviceYou lost me here. What I can say, is that using eg. "
xfs_reno-vpn /work", hence on the mount point directly, did as advertised.Cheers,
Pete
Sorry, the biggest problem is US daylight savings change and my simple brain. Waking this morning, it all mentally clicked. It is working as intended. Sorry for the noise.
--Mark.
--Mark.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs