Casper.Dik at Sun.COM
2007-Jun-07 21:40 UTC
[zfs-discuss] Moving files over with ufsrestore not that simple
After one aborted ufsrestore followed by some cleanup I tried
to restore again but this time ufsrestore faultered with:
bad filesystem block size 2560
The reason was this return value for the stat of "." of the
filesystem:
8339: stat(".", 0xFFBFF818) = 0
8339: d=0x03F50005 i=3 m=0040755 l=3 u=0 g=3 sz=3
8339: at = Jun 7 23:11:54 CEST 2007 [ 1181250714 ]
8339: mt = Jun 7 23:02:08 CEST 2007 [ 1181250128 ]
8339: ct = Jun 7 23:02:08 CEST 2007 [ 1181250128 ]
8339: bsz=2560 blks=3 fs=zfs
Blocksize of 2560??
Casper
Rich Teer
2007-Jun-07 21:43 UTC
[zfs-discuss] Moving files over with ufsrestore not that simple
On Thu, 7 Jun 2007, Casper.Dik at Sun.COM wrote:> 8339: stat(".", 0xFFBFF818) = 0 > 8339: d=0x03F50005 i=3 m=0040755 l=3 u=0 g=3 sz=3 > 8339: at = Jun 7 23:11:54 CEST 2007 [ 1181250714 ] > 8339: mt = Jun 7 23:02:08 CEST 2007 [ 1181250128 ] > 8339: ct = Jun 7 23:02:08 CEST 2007 [ 1181250128 ] > 8339: bsz=2560 blks=3 fs=zfs > > Blocksize of 2560??Hmm. 2560 = 2048 + 512; dunno if that i simportant or not... -- Rich Teer, SCSA, SCNA, SCSECA, OGB member CEO, My Online Home Inventory Voice: +1 (250) 979-1638 URLs: http://www.rite-group.com/rich http://www.myonlinehomeinventory.com
Matthew Ahrens
2007-Jun-14 06:56 UTC
[zfs-discuss] Moving files over with ufsrestore not that simple
Casper.Dik at sun.com wrote:> After one aborted ufsrestore followed by some cleanup I tried > to restore again but this time ufsrestore faultered with: > > bad filesystem block size 2560 > > The reason was this return value for the stat of "." of the > filesystem: > > 8339: stat(".", 0xFFBFF818) = 0 > 8339: d=0x03F50005 i=3 m=0040755 l=3 u=0 g=3 sz=3 > 8339: at = Jun 7 23:11:54 CEST 2007 [ 1181250714 ] > 8339: mt = Jun 7 23:02:08 CEST 2007 [ 1181250128 ] > 8339: ct = Jun 7 23:02:08 CEST 2007 [ 1181250128 ] > 8339: bsz=2560 blks=3 fs=zfsI could not reproduce this problem with some cursory testing (ufsdump|ufsrestore of a root filesystem). But feel free to file a bug against ufsrestore -- it shouldn''t care what the st_blocksize of a directory is. Perhaps it should be looking at struct statvfs''s f_bsize? --matt
Casper.Dik at sun.com
2007-Jun-14 08:43 UTC
[zfs-discuss] Moving files over with ufsrestore not that simple
>Casper.Dik at sun.com wrote: >> After one aborted ufsrestore followed by some cleanup I tried >> to restore again but this time ufsrestore faultered with: >> >> bad filesystem block size 2560 >> >> The reason was this return value for the stat of "." of the >> filesystem: >> >> 8339: stat(".", 0xFFBFF818) = 0 >> 8339: d=0x03F50005 i=3 m=0040755 l=3 u=0 g=3 sz=3 >> 8339: at = Jun 7 23:11:54 CEST 2007 [ 1181250714 ] >> 8339: mt = Jun 7 23:02:08 CEST 2007 [ 1181250128 ] >> 8339: ct = Jun 7 23:02:08 CEST 2007 [ 1181250128 ] >> 8339: bsz=2560 blks=3 fs=zfs > >I could not reproduce this problem with some cursory testing >(ufsdump|ufsrestore of a root filesystem). But feel free to file a bug >against ufsrestore -- it shouldn''t care what the st_blocksize of a directory >is. Perhaps it should be looking at struct statvfs''s f_bsize?The steps to reproduce are: - create directory - add some files - remove some files (compression enabled, if that matters) Casper