Bash脚本写入ls结果至其他目录失败求助

Hey there! Let's break down the most likely reasons your getDisk2 script isn't writing any output to the target location. Since you haven't shared the exact script code, I'll cover the common pitfalls based on your description:

1. Target Directory/File Permissions or Existence Issues #

• Missing target directory: Bash won't automatically create directories for you. If the directory where you want to save the output doesn't exist, the > redirection will fail. Add mkdir -p /path/to/target/dir to your script to ensure the directory exists (the -p flag creates parent directories too if needed).
• No write permissions: The user running the script (you, from /home/kai/) might not have permission to write to the target file or directory. Test this manually first: run echo "test content" > /path/to/your/target/file.txt from your terminal. If you get a "Permission denied" error, you'll need to adjust permissions (with chmod) or run the script with appropriate privileges (though avoid sudo unless absolutely necessary).

2. Incorrect Source Directory Path #

• If you're using a relative path to enter the source directory (e.g., cd disk2 instead of cd /full/path/to/disk2), the path will resolve relative to /home/kai/ (your working directory when running the script). If that relative path doesn't exist, the cd command fails—and if your script doesn't stop there, the subsequent ls will list files from /home/kai/ instead (or fail silently).
• Fix this by using an absolute path for the source directory, and add a check to ensure the cd succeeds:

  cd /absolute/path/to/source/dir || { echo "Failed to access source directory!"; exit 1; }
  

3. Wrong Output File Path #

• Same as the source directory issue: if your target file path is relative (e.g., disk2_files.txt instead of /var/log/disk2_files.txt), the file will be created in /home/kai/ instead of your intended location. Double-check that you're using an absolute path for the output file, or confirm the relative path is correct based on where you run the script.

4. Empty Source Directory #

• It sounds obvious, but if the directory you're running ls on has no files, the output file will be empty. Manually navigate to the source directory and run ls to verify there's content to capture.

5. Logic Issues in the getDisk2 Function #

• Maybe the function isn't being called at all? Or the ls and redirection are not properly chained. Here's a robust example of what your function could look like to avoid these issues:

  getDisk2() {
      # Define absolute paths (replace with your actual paths)
      local source_dir="/mnt/disk2"
      local target_file="/home/kai/output/disk2_file_list.txt"
  
      # Validate source directory exists
      if [ ! -d "$source_dir" ]; then
          echo "Error: Source directory $source_dir does not exist!"
          return 1
      fi
  
      # Create target directory if needed
      mkdir -p "$(dirname "$target_file")"
  
      # Run ls and write output, check for success
      cd "$source_dir" && ls -la > "$target_file"
      if [ $? -eq 0 ]; then
          echo "Success! Output saved to $target_file"
      else
          echo "Failed to write output to $target_file"
      fi
  }
  
  # Don't forget to call the function!
  getDisk2
  

6. Enable Debug Mode to See What's Happening #

• Add set -x at the very top of your script. This will print every command the script executes, including resolved paths and exit codes. Run the script again, and you'll be able to spot exactly where it's failing (e.g., a wrong path, a failed cd, etc.).

If you can share your actual script code, we can pinpoint the issue even faster!

内容的提问来源于stack exchange，提问作者K.Mazur