|
| (Documentation for the EXPERT Mode=JFS menu) |
|
|
|
|
| (to DFSee main pages) | File | Edit | Actions | Image | View | Scripts | Set | Help | (to BASIC menu) |
| Mode=FDISK | APFS | AUX | DUMPFS | EXTn | EFAT | FAT | HFS+ | HPFS | ISO | JFS | NTFS | REISER | SWAP | XFS |
Display a pseudo-graphical map of used versus free sectors in the filesystem
Display a usage map for the currently selected disk or filesystem
A pseudo-graphical map of the disk or partition allocation is
displayed, showing the distribution of data over the object
This is also an indication for the amount of unused sectors in
the object, that are beneficial to 'SMART-SECTOR' optimizations
in imaging and cloning operations.
The percentage of used sectors are displayed as a percentage at
the end of the line, and a total usage percentage and size is
shown just after the map itself.
For filesystems that support resizing, the limits for resizing
are shown after the map itself.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Find deleted/normal files, list and possibly recover them. HEX edit dir/file
This submenu offers selections to search for normal or deleted
files, display the resulting lists and possibly recover files.
It also offers selection to HEX-edit either the meta-information
for a file (Inode) or the actual file contents
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Find deleted files, then BROWSE the resulting list and copy files (UNDELETE)
This will find most files that have been deleted from a
filesystem and store the result in the sector-list.
The sectorlist is then used to BROWSE through the find results.
The dialog will allow 'actions' to be performed on the listed
files/directories, using <ENTER> to get the popup menu:
- View contents, as ASCII on File/Dir
- View as x86 Assembler - disassembly
- HEX-edit, contents only on File/Dir
- Edit Contents, autoview on File/Dir
- View OS/2 EA or Xattr on a File/Dir
- Edit DATA area sectors for File/Dir
- Edit META:Inode/Fnode/MFT/Dir-entry
- Edit the base filename for File/Dir
- Copy/Recover File(s) to other drive
- Reduce list to SELECTED files only
While deleted files can NOT be recoverd 'in-place' they CAN be
copied to another filesystem, in effect UNDELETING them with
the 'Copy/Recover' selection from the above menu.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Search for INODEs for deleted files, 'Recover from list' will UNDELETE them
This will search the whole partition for file INODEs that belong to
DELETED files, and that match the start of the filename specified.
The sectornumbers of the found INODEs will be added to the DFSee
sectorlist so can be used in later actions, or be exported to a file.
The files contained in that list can be RECOVERED to any directory
on the system, including a network, by using the 'RECOVER' command.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Search for INODEs for deleted or non-deleted files, for 'Recover from list'
This searches JUST the known INODE areas for INODEs of deleted
files (when 'Search OUTSIDE INODE area' is not specified,
or the whole partition (when 'Search OUTSIDE' IS specified, slow!)
where the given name matches the start of the filename specified.
The sectornumbers of the found INODEs will be added to the DFSee
sectorlist so can be used in later actions, or be exported to a file.
The files contained in that list can be RECOVERED to any directory
on the system, including a network, by using the 'RECOVER' command.
Note: The filenames to be found are recognizable ONLY when extra
information is available. In DFSee this can be any of:
- Name cache, automatically built with the SLT (and CHECK)
(SLT will be built automatically when not present yet)
- A .LONGNAME EA set for the file or Dir (June compatible)
- DFSee specific 'magic' names added to the filesystem Inodes
specifically for recovery and undelete. (CHECK -m command)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Search data area for INODEs for non-deleted files, for 'Recover from list'
This searches JUST the known INODE areas for INODEs of non-deleted
regular files (when 'Search OUTSIDE INODE area' is not specified,
or the whole partition (when 'Search OUTSIDE' IS specified, slow!)
where the given name matches the start of the filename specified.
The sectornumbers of the found INODEs will be added to the DFSee
sectorlist so can be used in later actions, or be exported to a file.
The files contained in that list can be RECOVERED to any directory
on the system, including a network, by using the 'RECOVER' command.
Note: The filenames to be found are recognizable ONLY when extra
information is available. In DFSee this can be any of:
- Name cache, automatically built with the SLT (and CHECK)
(SLT will be built automatically when not present yet)
- A .LONGNAME EA set for the file or Dir (June compatible)
- DFSee specific 'magic' names added to the filesystem Inodes
specifically for recovery and undelete. (CHECK -m command)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Find ANY file (Inode) even after (quick) formatting (slow, as last resort)
This allows searching for ANY Inodes including ones that are NOT from
the current FORMAT, so they have a different Inode Recovery Signature
(IRS) which is basically the timestamp of when the FS was formatted.
You can either specify the '0' wildcard value, to match ANY signature
or a specific one when known, to find only Inodes for that instance
of the filesystem (like only files from before formatting).
When listing or recovering files later, using an import list perhaps,
be sure to set this SAME IRS value, or Inodes will NOT be recognized!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Recognize ANY Inode even after (quick) formatting, allowing any signature
Browse files/directories in a list from a single directory, or current list
This will show the contents of a single directory, specified
by a PATH from the ROOT directory, or by selecting a directory
from the browse list itself (including the '..' directory).
Alternatively, the CURRENT contents of the sectorlist can be
browsed, when available (by specifying a '.' for the directory
The list can be browsed in an interactive dialog, a bit like
a regular filemanager.
The dialog will allow 'actions' to be performed on the listed
files/directories, using <ENTER> to get the popup menu:
- View contents, as ASCII on File/Dir
- View as x86 Assembler - disassembly
- HEX-edit, contents only on File/Dir
- Edit Contents, autoview on File/Dir
- View OS/2 EA or Xattr on a File/Dir
- Edit DATA area sectors for File/Dir
- Edit META:Inode/Fnode/MFT/Dir-entry
- Edit the base filename for File/Dir
- Copy/Recover File(s) to other drive
- Reduce list to SELECTED files only
When the browse session is ended (<Esc> or <F3> key):
- the SAME filesystem/partition stays selected
You can restart browse the same partition with the <F9> key,
or start browsing another partition from the Actions menu
using: 'Actions -> Open Partition, Browse FS'
- the sector-list contains the last browsed directory
and can be viewed with commands like 'list -f
- The last entry (file) that was selected will also be set
as the current sector-location ('this'), so it easy to
analyse that furthher, for example by using the HEX-editor
that can be started with <F2>, or simply by viewing the
sector using the <Enter> key.
Note: When working in 'mode=FDISK' (with a whole disk opened)
you will be presented with a selection-list to pick a
partition with a filesystem first.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Display (selected) files from the list, using a PATH+FILENAME wildcard
This will display the DFSee sector-list in a compact format, suited
to the data contained in the list
This usually is a 'list -f' or a 'list -s' variant.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Recover (selected) files from the list to a supplied recovery directory
This will allow you to recover (copy) one or more of the files in the
list to any local or network directory on your system.
It will prompt for a destination directory first, using the last used
one as a default. All files recovered in one go, will be recovered to
this same directory, with their original path appended to retain the
directory structure whenever possible.
It will also prompt for a selection specification in the form of a
full PATH+FILENAME wildcard and an optional allocation-percentage.
As an example, the specification:
'*mydoc*\*project_x*.doc%100'
will recover all files that have 'mydoc' somewhere in the PATH,
'project_x' in the filename and have an extension of '.doc' that
seem to be 100% recoverable. (100% allocation-OK ranking).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Add/Update filenames in the FS, for recovery/undelete (FS must be UNMOUNTED)
This submenu will execute a filesystem check (CHECK/SLT build)
with a special option that instructs it to ADD the found file
and directory names to an unused/reserved area in each INODE.
Since this actually WRITES to the filesystem, it is only effective
when the filesystem is in an UNMOUNTED, CLEAN state.
The added names, when present, will be used to allow display of
filename and full-PATH information, and use these for recovery
and UNDELETE as well.
Note: Filenames displayed in various places for the JFS filesystem
are recognizable ONLY when extra information is available.
(normally it is available in the JFS directories only.)
In DFSee this extra info can be any of:
- Name cache, automatically built with the SLT (and CHECK)
This allows for full path and filenames to be generated
whereever needed, but it DOES require basic JFS structures
to be consistent (not damaged too much).
- A .LONGNAME EA set for the file or Dir (June compatible)
This allows for display of file or directorynames, but not
always a full-path (since the parent directory is unknown)
The mechanism is compatible with the 'June/Jresquer' tools.
- DFSee specific 'magic' names added to the filesystem Inodes
specifically for recovery and undelete. (CHECK -m command)
This allows for full path and filenames to be generated
whereever needed, and does not even require a fully intact
JFS filesystem (some damage tolerated).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Recover the file associated with the CURRENT sector to a recovery directory
This will allow you to recover (copy) the file represented by the
CURRENT displayed sector, also called the 'THIS' sector to any local
or network directory on your system.
It will prompt for a destination directory first, using the last used
one as a default. The file will be recovered with its original path
appended to that to retain the directory structure whenever possible.
The menu item will only be enabled (selectable) when the CURRENT sector
represents a normal or deleted FILE for the filesystem involved.
This means it has to be a type 'f' or 'z' sector, which is:
For HPFS: an FNODE sector
For JFS: an INODE sector
For NTFS: an MFT record
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Find info (FNODE/MFT-record etc) for ONE specified file/directory path
This uses the specified path from the root-directory to locate
detailed information for the file or directory for that path.
This will be from the FNODE on HPFS, the MFT-record on NTFS or
similar structures like Inodes on other filesystrems.
The path and filename may contain spaces.
When found the information will be displayed in the standard
format as defined for the filesystem that is active.
You can display related information like the directory entry
or the actual file data from there using the U and D commands.
You can also use the 'saveto' command or corresponding menu
item 'Recover THIS file' to create a copy of this found file
on the specified or default recovery destination
(or use the combined menu option instead of this find :-)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Find ONE file by full path+filename, and recover it to a recovery directory
This uses the specified path starting from the ROOT to locate
ONE specific file, and when found will issue a SAVETO command
to recover the contents of this file to a recovery directory.
The path and filename may contain spaces.
Note:
The recovered file will be placed directly in the specified
recovery directory without the full original path, but with
the proper filename retained (even on JFS :-).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Find + edit FAT dir entry / HPFS fnode / JFS inode / NTFS MFTrec+small files
This uses the specified path from the root-directory to locate
information for the file or directory for that path.
This will be from the FNODE on HPFS, the MFT-record on NTFS or
similar structures like Inodes on other filesystrems.
The path and filename may contain spaces.
When found the information at THAT level (1st, direct)
will be opened in the standard HEX editor
This will often be META-data about the file or directory,
with a layout strongly defined by the filesystem type
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Find, then HEX edit most HPFS / JFS / NTFS file-data or directory contents
This uses the specified path from the root-directory to locate
information for the file or directory for that path.
This will be from the FNODE on HPFS, the MFT-record on NTFS or
similar structures like Inodes on other filesystrems.
The path and filename may contain spaces.
When found the information at the NEXT level (2nd, indirect)
will be opened in the standard HEX editor
This 'next' level is what would be displayed using a 'd' command
or using the ENTER key when the first level is being displayed.
It will often be data or contents for the file or directory.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Display/Edit Volume info like label, UUID, Serial-nr and dirty/clean status
This submenu offers several selections to Display or Edit Volume info
like label, UUID, serial-number, Signature and dirty/clean status
The UUID is a 16-byte unique identifier, used by Linux (on mounting)
There can be TWO labels present in a JFS filesystem:
- Standard (IBM) label, 11-characters (bootsector AND superblock)
- Linux specific label, 16-characters (superblock)
can be used as identification when mounting
The volume serial number should be a unique value in the system
The file system status can be one of:
- Unmounted - Clean When it is not in use, proper shutdown
- Mounted - Dirty When in use, and changes have been made
- Unmounted - Clean When in use, but no changes were made yet
In some cases, when CHKDSK fails, you can get (temporary) access
by manually setting the FS status to Unmounted-clean and reboot.
The FS version for an IBM OS/2 or eCS JFS should be numeric 1
The FS version for a Linux formatted JFS should be numeric 2
The signature string for an OS/2 or eCS or Linux should be 'JFS1'
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Display/Edit the standard 11-character label, as used by OS/2 and variants
This will present a small dialog to display and/or edit the
standard (IBM) label, with a maximum length of 11-characters
and located both in the BOOTSECTOR and the SUPERBLOCK
Both locations are updated simultaneously when editing
This standard label is used (on OS/2, ArcaOS, eComStation)
to identify the filesystem in commands like DIR and FORMAT
- Linux specific label, 16-characters (superblock)
can be used as identification when mounting
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Display/Edit the Linux 16-character label, as used with mounting the FS
This will present a small dialog to display and/or edit the
Linux specific label, with a maximum length of 16-characters
and located in the SUPERBLOCK
This Linux label is used (on Linux) to identify the filesystem
when mounting, instead of a devicename like /dev/sda1 or the
cryptic UUID
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Display and optionally edit the (Linux) UUID string value in the superblock
This will display and optionally update the UUID string in
the filesystems superblock.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Change the volume serial number, making this volume unique (after clone :-)
This will update the 'volume serial number' in the bootsector
This could be REQUIRED for some operating systems after cloning
a filesystem, to make sure the volume serial numbers are unique.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Update superblock status to indicate filesystem is UNMOUNTED and CLEAN
This will update the fileystem-status field in the JFS superblock
to indicate that filesystem is CLEAN, and not mounted.
This can be useful to avoid an automatic CHKDSK after a system-crash
Note: The filesystem itself is NOT cleaned in any way, it is just the
statusflag that is modified.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Update superblock status to indicate filesystem is DIRTY
This will update the fileystem-status field in the JFS superblock
to indicate that filesystem is DIRTY.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Update superblock status to indicate filesystem is MOUNTED and CLEAN
This will update the fileystem-status field in the JFS superblock
to indicate that filesystem is CLEAN, but IS mounted.
Note: The filesystem itself is NOT cleaned in any way,
it is just the statusflag that is modified.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Update superblock version-nr to IBM/eCS/Linux or explicit numeric value
This will display and optionally update the filesystem version
the filesystems superblock.
The FS version for an IBM OS/2 or eCS JFS should be numeric 1
The FS version for a Linux formatted JFS should be numeric 2
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Update superblock signature string to the default required 'JFS1' value
This will update the superblock signature string to the default
required 'JFS1' value.
This can be useful after CHDSK reporting both superblocks to be
corrupted, while only the signature has been scrambled ...
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Fix bootsector standard/bootable, HiddenSectors/GEO and JFS LDR sectors
This submenu offers selections for fixes related to booting like
fix the bootsector itself, JFS LDR image creation and restore
and fixing the HiddenSectors and geometry fields in the bootsector
This can be very useful when the bootsector got damaged by a virus
or a crashing program (writing to sector 0) or if the partition was
deleted by accident using FDISK or LVM and recreated again.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Write STANDARD (classic IBM) JFS Bootsector from partition+superblock-info
This will create a new JFS bootsector for the partition, based on
information from the partition-tables and on information found in
the superblock for the filesystem.
The bootsector code used is the STANDARD version, as originally
supplied by IBM. JFS partitions using this will not be bootable.
This can be very useful when the bootsector got damaged by a virus
or a crashing program (writing to sector 0) or if the partition was
deleted by accident using FDISK or LVM and recreated again.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Write BOOTABLE (ArcaOSn/eCS) JFS Bootsector from partition+superblock-info
This will create a new JFS bootsector for the partition, based on
information from the partition-tables and on information found in
the superblock for the filesystem.
The bootsector code used is the BOOTABLE version, as supplied with
ArcaOS and eComStation 2.x to allow booting from JFS partitions.
Apart from ths specific 'bootable' bootsector, you will also need
the JFS mini filesystem (mini-FS) in the sectors directly following
the bootsector itself. If not there yet, you can write that code
using other selections in this same menu.
This can be very useful when the bootsector got damaged by a virus
or a crashing program (writing to sector 0) or if the partition was
deleted by accident using FDISK or LVM and recreated again, or if
the partition was CHKDSK'ed by an OLD non-bootable UJFS.DLL ...
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Wipe the Bootsector, FIRST sector in a filesystem. Remove obsolete FS info
This will wipe the bootsector (first sector) of the selected
filesystem or partition.
Can be useful to get rid of old formatting infomation
that may confuse tools when trying to reformat.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Create compressed imagefile with the JFS LDR sectors for this partition
This will create a compressed imagefile with the JFS mini-FS
sectors from the current JFS partition, to be used later for
a restore to a damaged system.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Restore the imagefile with a 'known good' JFS LDR to current partition
This will restore an imagefile with the JFS mini-FS sectors to
the current JFS partition, to recover from a boot failure when
this code has been damaged somehow ...
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Fix bootsector HiddenSectors and geometry fields to match partition tables
This will update the 'hidden sectors' field in the bootsector
to match the offset to the partition-table the partition is
defined in and update the geometry Heads and Sectors field to
match the current disk geometry.
This could be REQUIRED for some operating systems like OS/2
to accept and mount the partition as a driveletter!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Make the currently selected PRIMARY the 'active' partition for MBR/BIOS boot
This will make the currently selected PRIMARY partition the
ACTIVE one for the disk.
There should only be a single active partition on every disk.
When the system starts, the BIOS will usually boot from
the ACTIVE partition on the first disk.
In IBM BMGR/LVM terms the active partition is called STARTABLE.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Delete the currently selected partition from the partition tables
This will delete the partition that is currently selected to be
deleted from the partition-tables. This will result in the space
occupied by the partition becoming FREESPACE that can be used
again to create new partitions.
For primary partitions on LVM-systems, the related LVM-information
is cleared as well, to avoid consistency problems later when a new
partition is created at the same position.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Display specified Inode sectors or Inode allocation information (IAG)
This submenu allows you to display information for Inodes,
eithe one specified by its Inode-number, or one of the special
one for the filesystem, like the ROOT-directory
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Display any Inode sector, by specifying the Inode-number
This will display information for the file or directory referenced
by the Inode-number specified.
This may include filenames, flags, date and time as well as
filespace allocation details.
Note: The Inode-sector has to be identified by its (hexadecimal)
Inode number, as found in directory details or 'well-known'
ones like 02 for the root-directory.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Extension area for the filesystem1 super-inode (Aggregate inode at LSN 68)
Extension area for the filesystem1 super-inode (seldom needed)
It extends the agregate inode at LSN 68, mapping used Inodes
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
RootDir, main index to the volumes regular files and directories in fileset1
RootDir, main index to the volumes regular files and
directories in fileset1 (the one and only :-)
This is a normal Inode for a directory, but since it is the root
of the directory/file tree, it is the most important one to find
anything by name ...
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Special data file with consolidated Access Control List for the fileset
Special data file with consolidated Access Control List for the fileset
Regular file and directory Inodes may contain ACL info that usually
indexes into the data in this file.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Aggregate super or 'self' inode, describing the Aggregate Inode Map blocks
Aggregate 'self' inode, describing the Aggregate Inode Map blocks
Needed to find an aggregate Inode based on its inode number.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Aggregate inode with the bitmap structures that map the whole aggregate
Aggregate inode with the bitmap structures that map the whole aggregate
This systemfile is crucial for displaying the allocation map,
and to determine proper allocation for normal/deleted files
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Aggregate inode with blocks allocated to areas detected as 'bad' on format
Aggregate inode with blocks allocated to areas
detected as 'bad' on format
This effectively avoids these blocks from being used for other files
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Aggregate inode with the Fileset1 Allocation Map, mapping the Inode extents
Aggregate inode with the Fileset1 Allocation Map,
mapping the Inode extents used for regular inodes
It is needed to allow translation between Inode numbers
and their sector number
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Display summary info on all IAG's, or detailed info on a specified IAG nr
Display information about Inode Allocation Groups
Without a number specified, it will list all IAG's
summarizing the number of Inodes per IAG and some
info on the location and inode range used.
With a number specified, the header info for that
IAG structure will be displayed and verified, and
an overview of where the inodes are allocated on disk
Checking the 'verbose' option will cause extra info
to be displayed for the header fields that may allow
repair of a damaged structure.
Checking the 'Aggregate' option will display the info for
the aggregate (system) inodes instead of the fileset-1
(user) ones.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Dump the JFS system areas, Aggr/Fs1 inodes to file for analysis by support
This will create a binary dump for the start of the filesystem
which will include the superblocks and aggregate/fileset inodes.
Quite useful for later analysis, perhaps by DFSee support.
The usual IMAGE dialog will be presented, with the startsector
and size filled in, as well as a suggested filename.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Display the SUPERBLOCK structure for the currently selected filesystem
This will display the contents of the filesystem superblock
in a textual format matching the current filesystem type.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Check filesystem for inconsistencies and errors (Readonly, no fixing!)
This will perform a CHECK of the filesystem, somewhat like the
well-known CHKDSK but without automatically fixing anything.
The result of the check is a sector-lookup-table (SLT) that contains
information about all recognized filesystem areas that are in use.
Any error recognized will be flagged in the default display of
this SLT that is performed automatically by the CHECK command.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Create Sector Lookup Table (SLT) if needed, display as table or sector info
This submenu allows you to build and inspect a 'Sector lookup Table'
or SLT, that collects some info about each identifiable sector range
in the currently selected filesystem.
The SLT is the basis required to identify specific sectors, showing
to what file or FS-metadata it belongs, and for the CHECK command.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Show layout of current object by displaying parts of the Sector Lookup Table
This will display part of the sector-lookup-table (SLT)
You wil be presented with an option dialog first, where you
specify the desired format and part of the SLT to be displayed.
The SLT will be built automatically if not done yet, and it will
have been built by any previous CHECK command too.
Building the SLT will take place in the background while the
dialog can be used freely to specify any options for displaying.
After the dialog has been ended, and the SLT is ready, it will
be displayed as requested.
Typically the SLT will contain at least one entry for every file
on the filesystem, so there could be hundreds of thousands lines!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Show identification for specified (or current) sector, using the SLT
This will display information about the specified sector that is
available in the sector lookup table (SLT)
The most useful info is the sector referencing this sector, this
often leads to showing to which file/directory the sector belongs.
The SLT will be generated automatically if not yet available
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Show identification for the last sector used, dictating the minimum FS size
This will display information about the sector that is the last
one being used (allocated) in the filesystem, and because of that
dictates the MINIMUM size for the filesystem for a RESIZE.
The most useful info is the sector referencing this sector, this
often leads to showing to which file/directory the sector belongs.
The SLT will be generated automatically if not yet available,
just as the required allocation information (alloc).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
Unselect filesystem, reselect the same/first disk; enables Mode=FDISK menu
This will UNSELECT the current object/filesystem, and reselect a
whole physical disk, either the same disk as the partition was on,
or the first disk present in other cases.
This is a quick way to change to 'Mode=FDISK' and work on
disk-level issues
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press <F1> again for more help; Some options may require switching to 'Expert mode'
| (to DFSee main pages) | File | Edit | Actions | Image | View | Scripts | Set | Help | (to BASIC menu) |
| Mode=FDISK | APFS | AUX | DUMPFS | EXTn | EFAT | FAT | HFS+ | HPFS | ISO | JFS | NTFS | REISER | SWAP | XFS |
| (Mode=JFS page) | DFSee menu documentation for pulldown : Mode=JFS |
| Views: 617146 |
|
Created by Jan van Wijk: Aug 2007, last update: 23-Oct-2022 |
|